Tue Apr 23 18:18:34 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2004-09-01

HANGOUT

2024-04-23 | 2024-03-23 | 2024-02-23 | 2024-01-23 | 2023-12-23 | 2023-11-23 | 2023-10-23 | 2023-09-23 | 2023-08-23 | 2023-07-23 | 2023-06-23 | 2023-05-23 | 2023-04-23 | 2023-03-23 | 2023-02-23 | 2023-01-23 | 2022-12-23 | 2022-11-23 | 2022-10-23 | 2022-09-23 | 2022-08-23 | 2022-07-23 | 2022-06-23 | 2022-05-23 | 2022-04-23 | 2022-03-23 | 2022-02-23 | 2022-01-23 | 2021-12-23 | 2021-11-23 | 2021-10-23 | 2021-09-23 | 2021-08-23 | 2021-07-23 | 2021-06-23 | 2021-05-23 | 2021-04-23 | 2021-03-23 | 2021-02-23 | 2021-01-23 | 2020-12-23 | 2020-11-23 | 2020-10-23 | 2020-09-23 | 2020-08-23 | 2020-07-23 | 2020-06-23 | 2020-05-23 | 2020-04-23 | 2020-03-23 | 2020-02-23 | 2020-01-23 | 2019-12-23 | 2019-11-23 | 2019-10-23 | 2019-09-23 | 2019-08-23 | 2019-07-23 | 2019-06-23 | 2019-05-23 | 2019-04-23 | 2019-03-23 | 2019-02-23 | 2019-01-23 | 2018-12-23 | 2018-11-23 | 2018-10-23 | 2018-09-23 | 2018-08-23 | 2018-07-23 | 2018-06-23 | 2018-05-23 | 2018-04-23 | 2018-03-23 | 2018-02-23 | 2018-01-23 | 2017-12-23 | 2017-11-23 | 2017-10-23 | 2017-09-23 | 2017-08-23 | 2017-07-23 | 2017-06-23 | 2017-05-23 | 2017-04-23 | 2017-03-23 | 2017-02-23 | 2017-01-23 | 2016-12-23 | 2016-11-23 | 2016-10-23 | 2016-09-23 | 2016-08-23 | 2016-07-23 | 2016-06-23 | 2016-05-23 | 2016-04-23 | 2016-03-23 | 2016-02-23 | 2016-01-23 | 2015-12-23 | 2015-11-23 | 2015-10-23 | 2015-09-23 | 2015-08-23 | 2015-07-23 | 2015-06-23 | 2015-05-23 | 2015-04-23 | 2015-03-23 | 2015-02-23 | 2015-01-23 | 2014-12-23 | 2014-11-23 | 2014-10-23 | 2014-09-23 | 2014-08-23 | 2014-07-23 | 2014-06-23 | 2014-05-23 | 2014-04-23 | 2014-03-23 | 2014-02-23 | 2014-01-23 | 2013-12-23 | 2013-11-23 | 2013-10-23 | 2013-09-23 | 2013-08-23 | 2013-07-23 | 2013-06-23 | 2013-05-23 | 2013-04-23 | 2013-03-23 | 2013-02-23 | 2013-01-23 | 2012-12-23 | 2012-11-23 | 2012-10-23 | 2012-09-23 | 2012-08-23 | 2012-07-23 | 2012-06-23 | 2012-05-23 | 2012-04-23 | 2012-03-23 | 2012-02-23 | 2012-01-23 | 2011-12-23 | 2011-11-23 | 2011-10-23 | 2011-09-23 | 2011-08-23 | 2011-07-23 | 2011-06-23 | 2011-05-23 | 2011-04-23 | 2011-03-23 | 2011-02-23 | 2011-01-23 | 2010-12-23 | 2010-11-23 | 2010-10-23 | 2010-09-23 | 2010-08-23 | 2010-07-23 | 2010-06-23 | 2010-05-23 | 2010-04-23 | 2010-03-23 | 2010-02-23 | 2010-01-23 | 2009-12-23 | 2009-11-23 | 2009-10-23 | 2009-09-23 | 2009-08-23 | 2009-07-23 | 2009-06-23 | 2009-05-23 | 2009-04-23 | 2009-03-23 | 2009-02-23 | 2009-01-23 | 2008-12-23 | 2008-11-23 | 2008-10-23 | 2008-09-23 | 2008-08-23 | 2008-07-23 | 2008-06-23 | 2008-05-23 | 2008-04-23 | 2008-03-23 | 2008-02-23 | 2008-01-23 | 2007-12-23 | 2007-11-23 | 2007-10-23 | 2007-09-23 | 2007-08-23 | 2007-07-23 | 2007-06-23 | 2007-05-23 | 2007-04-23 | 2007-03-23 | 2007-02-23 | 2007-01-23 | 2006-12-23 | 2006-11-23 | 2006-10-23 | 2006-09-23 | 2006-08-23 | 2006-07-23 | 2006-06-23 | 2006-05-23 | 2006-04-23 | 2006-03-23 | 2006-02-23 | 2006-01-23 | 2005-12-23 | 2005-11-23 | 2005-10-23 | 2005-09-23 | 2005-08-23 | 2005-07-23 | 2005-06-23 | 2005-05-23 | 2005-04-23 | 2005-03-23 | 2005-02-23 | 2005-01-23 | 2004-12-23 | 2004-11-23 | 2004-10-23 | 2004-09-23 | 2004-08-23 | 2004-07-23 | 2004-06-23 | 2004-05-23 | 2004-04-23 | 2004-03-23 | 2004-02-23 | 2004-01-23 | 2003-12-23 | 2003-11-23 | 2003-10-23 | 2003-09-23 | 2003-08-23 | 2003-07-23 | 2003-06-23 | 2003-05-23 | 2003-04-23 | 2003-03-23 | 2003-02-23 | 2003-01-23 | 2002-12-23 | 2002-11-23 | 2002-10-23 | 2002-09-23 | 2002-08-23 | 2002-07-23 | 2002-06-23 | 2002-05-23 | 2002-04-23 | 2002-03-23 | 2002-02-23 | 2002-01-23 | 2001-12-23 | 2001-11-23 | 2001-10-23 | 2001-09-23 | 2001-08-23 | 2001-07-23 | 2001-06-23 | 2001-05-23 | 2001-04-23 | 2001-03-23 | 2001-02-23 | 2001-01-23 | 2000-12-23 | 2000-11-23 | 2000-10-23 | 2000-09-23 | 2000-08-23 | 2000-07-23 | 2000-06-23 | 2000-05-23 | 2000-04-23 | 2000-03-23 | 2000-02-23 | 2000-01-23 | 1999-12-23

Key: Value:

Key: Value:

MESSAGE
DATE 2004-09-10
FROM Ruben Safir Secretary NYLXS
SUBJECT Subject: [hangout] INDUCE: Copyright Office Recommended Statutory Language


The following effort to change copyright law MUST be opposed, and
everyone should call their
Congressmen now about this bill, and run off a paper mail to Washington
in opposition to this
law.

Do NOT be decieved by the preceived benigness of this statute, about
willfulness etc.
This Bill will flatout make everyone who ever wrote a peice of Software
to distribute information
eligible for legal extortion. Everyone knows that when a well funded
organization wants to
kill something, may it be a private patent, or copyright, they simply
drag you through the courts
until your broke and broken.

It will be up to YOU to prove your intent in court!!!!


Ruben



RECOMMENDED STATUTORY LANGUAGE

Section 501 of title 17, United States Code, is amended by adding
at the end the following:

(g)(1) INDUCEMENT OF INFRINGEMENT - Whoever manufactures, offers
to the public, provides, or otherwise traffics in any product or
service, such as a computer program, technology, device or
component, that is a cause of individuals engaging in infringing
public dissemination of copyrighted works shall be liable as an
infringer where such activity:

(A) relies on infringing public dissemination for its commercial
viability;

(B) derives a predominant portion of its revenues from infringing
public dissemination; or

(C) principally relies on infringing public dissemination to
attract individuals to the product or service.

(2) For the purposes of this subsection, "public dissemination"
means digital transmission to the public of copies or
phonorecords or any other exercise of any of the rights set
forth in sections 106(3), 106(4), 106(5) or 106(6).

(3) LIMITATIONS ON REMEDIES - (A) No award of statutory damages
under Section 504(c) shall be made for a violation of this
subsection unless the copyright owner sustains the burden of
proving, and the court finds, that such violation was committed
willfully. (B) In granting injunctive relief under Section 502
for a violation of this subsection, the court shall, to the
extent practicable, limit the scope of the injunctive relief so
as not to prevent or restrain noninfringing uses of the product
or service.

(4) Nothing in this subsection shall enlarge or diminish the
doctrines of vicarious liability and contributory infringement,
including any defenses thereto or any limitations on rights or
remedies for infringement. Nothing in this subsection shall
enlarge or diminish liability for infringement of the exclusive
rights in sections 106(1) or 106(2).

EXPLANATORY MEMORANDUM

Introduction

In developing this recommendation, the Copyright Office reviewed
comments from and engaged in constructive discussions with a
wide variety of interested parties, including American
Federation of Television and Radio Artists, Association of
American Publishers, Broadcast Music, Inc., Business Software
Alliance, Center for Democracy & Technology, Consumer
Electronics Association, Corbis, Digital Future Coalition,
Digital Media Association, Distributed Computing Industry
Association, Entertainment Software Association, Future of Music
Coalition, IBM, IEEE, Information Technology Association of
America, Internet Commerce Coalition, Motion Picture Association
of America, NetCoalition, Public Knowledge, Recording Artists
Coalition, Recording Industry Association of America, Software
and Information Industry Association, Sun Microsystems, Verizon,
and the Video Software Dealers Association. Senate Judiciary
staff met with several groups individually to discuss the bill
and examine proposed changes, and they shared the results of
those meeting with us. We reviewed the thoughtful proposals for
statutory language submitted by IEEE, NetCoalition, Consumer
Electronics Association and the Business Software Alliance.

After the individual meetings held by Committee staff, Jule L.
Sigall, Associate Register for Policy & International Affairs,
moderated a group meeting in late August with interested parties
identified by the staff. At this meeting, the various
alternatives and ideas contained in the proposals were discussed
with the parties in a constructive dialogue. Based on that
discussion and the written proposals, the Copyright Office
circulated a discussion draft to the parties that was intended
to reflect the ideas discussed in the meeting in more concrete
terms. We made clear that this discussion draft was not a draft
of the Office's recommendation; rather, it was designed to
provoke comment and feedback on the many different concepts put
forth in the various proposals so that the Office could be fully
informed on the parties' views on all aspects of this issue.

We received written comments from nearly all of the interested
parties on the discussion draft, and held a meeting on September
7 to discuss those comments with the parties. Several groups
who commented on the discussion draft but were not originally
identified by Committee staff as participants requested to and
did participate in that meeting. In all cases, these meetings
and discussions were highly constructive, with the parties
considering the issues forthrightly and providing thoughtful
feedback and information on the many different issues involved.

Description of Recommendation

This recommendation reflects an effort to meet the goals
expressed for this legislation by the cosponsors of S. 2560 at
the July 22 hearing and in their August 13 letter. First, the
bill should be technology-neutral, and should not impose
liability based on the use of any particular technology but on
the circumstances in which that technology is used. Second, it
should provide an effective cause of action against those
services who today are establishing massive networks of
copyright infringement through the use of peer-to-peer
technology, but be flexible enough to accommodate new,
unforeseen situations in the future. Third, the bill should not
chill innovation by unnecessarily creating the threat of
liability for developers and distributors of technology who are
not engaged in encouraging and profiting from copyright
infringement. Fourth, the bill should also preserve the
decision by the Supreme Court in Sony Corp. v. Universal City
Studios, Inc., 464 U.S. 417 (1984), often referred to as the
Betamax case. We have strived to meet all of these goals in our
recommendation, despite the great difficulty that exists in
reconciling these important and sometimes conflicting issues.

In light of the variety of conflicting proposals put forth by
the parties and the many issues involved, it was not possible to
achieve consensus for this recommendation in the time we had.
What we have attempted to do is recommend an approach that
accommodates the legitimate concerns of all the parties, and
therefore we believe it presents the best chance to serve as
basis for developing consensus for this legislation.

Our effort to develop consensus proposals began with the text of
S. 2560, and we engaged in a discussion with the interested
parties of additional language that would clarify the scope of
the bill and assuage concerns of technology companies and others
about its application. The bill as introduced reflects a
"behavior-based" approach, which has the decided advantage of
focusing not on the technology involved but on the defendant's
actions. NetCoalition and IEEE offered alternatives that would
codify all secondary liability doctrines, including a form of
inducement liability. Another approach was offered by Consumer
Electronics Association, which would create liability for a
narrow class of activity of distributing a computer program
specifically designed to encourage mass, indiscriminate
infringing distribution. The Business Software Alliance
proposed changes to S. 2560 that it asserted would make the bill
more specific and give more comfort to technology companies
about the scope of liability under the bill. Our discussion
draft attempted to capture as many of the concepts in these
proposals as possible so that we could hear the parties' views
on them before making our recommendation.

A concern raised by technology companies about the
behavior-based approach was that it did not provide enough
guidance on what activity was subject to liability and what was
not. Also, it was claimed that an approach that focused on
intent would likely not be susceptible to summary adjudication,
but would require expensive jury trials for resolution of the
liability question. To address these concerns, some parties
offered the CEA proposal as an alternative, claiming that it
offered more objectivity and a clearer standard of liability,
even though it, by its terms, contains elements of intent and
behavior, and an element examining the design of technology. Our
discussion draft provoked many comments, and parties on both
sides had concerns about many of the provisions. One concept
that did not draw much criticism, and garnered some support from
one technology group, was a provision that made liability turn
on whether the defendant provided technology as part of an
operation that relied on infringement for its commercial
viability or for a predominant portion of its revenues. The CEA
proposal also contains a variation of this concept, albeit used
in a different context.

After serious consideration of the issues raised by these
alternative approaches, we have concluded that none of these
approaches by itself accommodates the legitimate concerns of all
parties and meets the goals described above. However, each has
positive aspects to it that have contributed to our
recommendation. We have concluded that enacting a separate form
of liability, as S. 2560 would, is the preferable course to
take, rather than codifying all forms of secondary liability,
given the long history these existing doctrines have and the
myriad of additional issues that would be raised if their
codification were considered as part of this effort. We started
with the general concept in the CEA proposal of clearly
identifying the activity that creates liability, but modified
that draft substantially to make it meet the goals described
above, particularly the goal of creating a form of liability
that can accommodate changes in the way technology is used in
the future.

This approach focuses neither on technology nor behavior
generally, but specifically on the business model in which a
technology is employed, essentially revolving around the
question of whether the defendant is relying on infringement to
build a business around its product or service. Our decision
was based in part on the relatively positive feedback described
above that we received on this "business model" concept. We
believe that this approach best serves the goal of both
capturing the existing peer-to-peer services built on widespread
infringement, yet remaining flexible enough to address potential
use of new technology by "bad actors" in the future that we
cannot predict right now, just as we could not predict the
imminent phenomenon of massive infringement by means of
peer-to-peer when the Digital Millennium Copyright Act was
enacted in 1998. Experience has taught us that legislation that
focuses on a particular technology is likely to be obsolescent
from the moment it is enacted, and waiting to enact new
legislation to address new technological developments inevitably
is a Sisyphysian effort.

Subsection 501(g)(1)

Our recommendation would create a new subsection (g) to section
501 of the Copyright Act. The operative provision on liability
is set forth in paragraph (g)(1). This provision narrows the
existing bill considerably, as it only applies to situations
where technology is employed as a cause of "infringing public
dissemination." As explained below, "public dissemination" is
defined in paragraph (2) to exclude direct infringement that
implicates only the reproduction or derivative work rights. In
other words, this recommendation would not impose liability on
any product or service that is a cause of only private
reproductions, such as the VCR, CD-burners, or the typical
portable music player. Liability, if any, for conduct related
to such personal reproduction technology remains the province of
existing copyright law, and is not affected in any way by this
new form of liability. Furthermore, liability would be imposed
only in one of three circumstances, each of which turns on the
importance of the infringing use of the product or service to
the defendant's commercial interest or efforts to attract the
public to their product or service. Liability would result if
the technology is "a cause" of individuals engaging in
infringing public dissemination of copyrighted works. We
considered predicating liability on whether the defendant has
"induced" or "caused" infringement, but after careful
consideration concluded that neither of those words clearly
expresses the appropriate causal connection between the actions
of the defendant and the infringing acts of a third party.
Although the theory of liability is based on concepts of
inducement, as reflected in the caption of subsection (g)(1),
discussions on this issue revealed a great deal of concern over
the precise meaning of the term "induce" and little agreement
over what the meaning of that term as used in the bill should
be. Predicating liability on whether the defendant "causes"
infringement could be interpreted as requiring that the
defendant's conduct be the proximate or ultimate cause of the
infringement, which we rejected as too high a burden. Obviously,
the proximate cause of any act of infringement is most likely
going to be the volitional act of the individual who engaged in
the infringement, rather than any acts of a person who has
induced an individual to infringe. We concluded that, combined
with the three conditions set forth in subparagraphs
(g)(1)(A)-(C), simply requiring that the defendant's conduct be
"a cause" of the infringement reflects the appropriate balance.

The key factor in determining liability lies in the three
conditions, at least one of which must be met, in order for
liability to be imposed. Each of these conditions set forth in
subparagraphs (g)(1)(A)-(C) turns on the importance of the
infringing use of the product or service to the defendant's
commercial interest or efforts to attract the public to its
product or service. The third condition in subparagraph (C)
would allow liability to be imposed where a defendant attracts
consumers to its product or service primarily through
infringement but has not undertaken the activity for commercial
purposes.

The approach taken here seeks to avoid the controversial issues
surrounding the various alternatives and focus liability on the
business model adopted by the defendant. If the defendant
distributes its product or service as part of an enterprise that
relies on infringement to attract customers, remain commercially
viable or earn a predominant portion of its revenues, it will be
liable under this provision. Under this approach, there is no
need for the courts to get into thorny questions about how a
particular technology was designed, what its particular
functions can or can't do, or difficult questions of intent. In
essence, this approach determines whether inducement has
occurred through an objective test of how the technology is
deployed as part of the defendant's business.

The analysis under these three provisions would focus on the
defendant's "activity" of manufacturing, distributing or
providing the product or service, and in cases where a
particular activity is a part of a larger operation, the court
should isolate the defendant's activity that is a cause of the
infringement at issue from the rest of the organization for
purpose of analyzing whether any of the three conditions apply.
For example, if a large software and services company has a
division that begins distributing a device that is a cause of
infringing dissemination, the revenues and commercial viability
of the other parts of the company would not be considered in the
analysis of subparagraphs (g)(1)(A)-(C); thus, whether or not an
entire organization's revenues are derived from infringement
would have no bearing on liability, but only whether the
activity in question depends on infringement for its commercial
viability or that activity's revenues predominantly derive from
infringement. We intend "derives a predominant portion of its
revenues from infringing public dissemination" to mean that more
of the revenues from that particular activity can trace their
origin to infringing public dissemination (e.g. to purchases by
persons who are using the product or service for purposes of
infringing public dissemination) that to all other sources; i.e.
more than fifty percent of revenues are derived from infringing
public dissemination.

Section 501(g)(2)

Paragraph (2) defines "public dissemination" as the exercise of
the so-called "public" rights under copyright: distribution of
copies to the public, public performance, public display and
public performance of sound recordings by means of digital audio
transmission. It also makes clear that distribution by digital
transmission to the public is covered, to leave no doubt that
the form of infringing distribution occurring on peer-to-peer
services falls within the form of direct infringement that
serves as a predicate for liability under this new provision.
The term "digital transmission" is already defined in section
101 of the statute, and a similar formulation to that here is
used in Section 115(c)(3)(A), which makes clear that the
mechanical compulsory license includes the right to "distribute
or authorize the distribution of a phonorecord … by means of a
digital transmission …." See also, e.g., A&M Records, Inc. v.
Napster, Inc., 239 F.3d 1004, 1014 (9th Cir. 2001). We have
also included the public performance and public display rights
to cover services that do not distribute copies but still
infringe by making works available to the public in the form of
performances and displays, such as peer-to-peer webcasting
services. However, the mere infringement of the reproduction
right or the derivative work right, without any of these
additional elements, would not constitute "public
dissemination." This should allay the concerns of those who
fear that the legislation could be used to target manufacturers
and marketers of devices used for personal copying.

Section 501(g)(3)

Because paragraph (1) makes those liable under this subsection
as "an infringer," all of the remedies available under Chapter 5
of the Copyright Act are available in actions under this
subsection. However, paragraph (3) provides two important
limitations on those remedies, one of which is based on a
proposal made by IEEE regarding limitations on monetary relief.
First, statutory damages, of any level, are not available for
violations of this new provision unless the copyright owner
proves that the violation of subsection (g)(1) was willful.
This provision was drafted to address concerns raised by
technology companies that the specter of liability under this
theory might chill innovation, and a limitation on statutory
damages should help to ally those concerns, since a nonwillful
violator would only be liable for the actual damages and lost
profits that the plaintiff could prove the defendant had
caused. Also responsive to this concern is the existing Section
505 of the Copyright Act, which allows a court to award
attorney's fees to a prevailing defendant in "any civil action"
under title 17, which would include this new form of liability.
Second, a court that issues an injunction under this subsection
must, where practicable, fashion the scope of the injunction not
to restrain or prevent the noninfringing uses of the product or
service at issue. This is a critical aspect of the Sony
decision, which sought to prevent copyright liability from
inhibiting the noninfringing use of technology. Thus, in the
peer-to-peer context, an injunction might prohibit those features
of a peer-to-peer service that cause infringement, but would not
prohibit the service or the technology itself.

Section 501(g)(4)

This paragraph provides savings clauses to ensure that this new
form of liability does not affect the existing doctrines of
secondary liability, as well as the defenses and limitations on
remedies for such liability. It also makes clear that this new
provision does not affect existing law of liability for
infringement of the rights of reproduction and preparing
derivative works, which are not predicate acts for liability
under this recommendation.

As with the remedies provisions in Chapter 5, which are fully
applicable to this new cause of action, the limitations on
liability in Section 512 also apply fully to this new
provision. Thus, even in the unlikely case that a qualifying
"service provider" would meet the criteria for liability under
this provision, it would still be entitled to the limitations on
liability in Section 512, if it met the conditions of those
provisions. Like the new form of liability contained in the CEA
proposal, the recommendation does not make the defense
recognized in the Sony decision regarding capability of
noninfringing uses applicable to this new form of liability.
Application of the Sony defense to this new form of liability is
unnecessary, as the concerns underlying that decision are
accommodated in this recommendation. First, the
recommendation's narrowed scope, addressing technologies of
"public dissemination," confines it to circumstances not present
in the Sony case, which involved personal copying technology in
the form of the VCR, not distribution technology. Second,
liability under this provision does not turn on a product's or
service's capabilities, features or design - rather, it depends
on the business model in which that product or service is
offered. The very same technology may result in liability when
offered by one defendant and not result in liability when
offered by another, depending on how each defendant relies on
the infringing use of the technology to attract consumers or
earn revenues. In this way, the recommendation avoids the
concern expressed by groups like IEEE and BSA over having the
courts engage in searching review of a technology's design or
capabilities to determine liability. Third, as noted above, the
limitation on injunctive relief that requires a court to
accommodate noninfringing uses as much as practicable vindicates
the most important concern underlying the Sony case - that
unrelated areas of commerce not be burdened by copyright
liability. Fourth, the savings clause makes clear that Sony
remains fully applicable to causes of action under the existing
doctrines of secondary liability.

--------------------------------------------------------------------
James S. Tyre
mailto:jstyre-at-jstyre.com
Law Offices of James S. Tyre
310-839-4114/310-839-4602(fax)
10736 Jefferson Blvd., #512 Culver City, CA
90230-4969
Co-founder, The Censorware Project
http://censorware.net



-
____________________________
NYLXS: New Yorker Free Software Users Scene
Fair Use -
because it's either fair use or useless....
NYLXS is a trademark of NYLXS, Inc

  1. 2004-09-30 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] New York Linux Scene (fwd)
  2. 2004-09-30 Michael Richardson <MRichardson-at-abc.state.ny.us> Subject: [hangout] RE: [fairuse-talk] MS FAT Patent Overruled by USPTO
  3. 2004-09-30 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Is there a meeting tonight?
  4. 2004-09-30 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] FW: MANDATORY MILITARY DRAFT 2005
  5. 2004-09-30 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] FW: MANDATORY MILITARY DRAFT 2005
  6. 2004-09-30 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] More Desktop News
  7. 2004-09-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Jounal Committee Meeting Tomorrow
  8. 2004-09-28 From: "Ruben I Safir - Secretary NYLXS" <ruben-at-mrbrklyn.com> RE: [hangout] NYLXS Board Meeting Report
  9. 2004-09-28 From: "Ruben I Safir - Secretary NYLXS" <ruben-at-mrbrklyn.com> Subject: [hangout] Munich Update
  10. 2004-09-28 From: "Ruben I Safir - Secretary NYLXS" <ruben-at-mrbrklyn.com> Subject: [hangout] Desktop Stratergies
  11. 2004-09-28 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] NYLXS Board Meeting Report
  12. 2004-09-28 Michael Richardson <MRichardson-at-abc.state.ny.us> Subject: [hangout] FW: MANDATORY MILITARY DRAFT 2005
  13. 2004-09-28 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [Fwd: Only two weeks to go --- Register Now] (fwd)
  14. 2004-09-27 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] (fwd) [SECURITY] [DSA 554-1] New sendmail packages fix
  15. 2004-09-27 Adam Kosmin <akosmin-at-nyc.rr.com> Subject: [hangout] (fwd) [SECURITY] [DSA 554-1] New sendmail packages fix potential open relay
  16. 2004-09-27 Ruben Safir <ruben-at-mrbrklyn.com> Re: [hangout] Paging Rob M
  17. 2004-09-27 Adam Kosmin <akosmin-at-nyc.rr.com> Re: [hangout] High-tech job market lost 400,000 jobs
  18. 2004-09-27 Billy <billy-at-dadadada.net> Re: [hangout] Paging Rob M
  19. 2004-09-27 Billy <billy-at-dadadada.net> Re: [hangout] Paging Rob M
  20. 2004-09-27 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] (fwd) [SECURITY] [DSA 554-1] New sendmail packages fix potential open relay
  21. 2004-09-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] SpamAssassin dccproc
  22. 2004-09-26 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] [Fwd: [Politics] FW: Interesting approach to stress]
  23. 2004-09-26 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Computer crash forces cancled flights.
  24. 2004-09-26 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Weekly NYLXS Announcments
  25. 2004-09-25 Billy <billy-at-dadadada.net> Re: [hangout] UID weirdness
  26. 2004-09-25 Billy <billy-at-dadadada.net> Re: [hangout] UID weirdness
  27. 2004-09-25 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [DMCA_Discuss] NY Judge Repudiates Live Music Bootleg Law (fwd)
  28. 2004-09-25 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [Fwd: [Politics] FW: Interesting approach to stress] (fwd)
  29. 2004-09-25 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] UID weirdness
  30. 2004-09-24 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  31. 2004-09-24 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  32. 2004-09-24 From: "P.Robert Marino" <rob-at-concord-hs.org> RE: [hangout] SuSE Ent9 Server & YOU
  33. 2004-09-24 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] MS sues spammers webhosters.
  34. 2004-09-24 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] MS sues spammers webhosters.
  35. 2004-09-24 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [DMCA_Discuss] First Amendment Defense Fails in DVD Copy Control
  36. 2004-09-23 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] SpamAssassin sports new open-source license
  37. 2004-09-23 Adam Kosmin <akosmin-at-nyc.rr.com> Re: [hangout] SuSE Ent9 Server & YOU
  38. 2004-09-23 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  39. 2004-09-23 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] SpamAssassin sports new open-source license
  40. 2004-09-22 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  41. 2004-09-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Novell recruit MS talent for GNU/Linux marketing
  42. 2004-09-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Sun Open Source stratergy of the day
  43. 2004-09-22 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] SuSE Ent9 Server & YOU
  44. 2004-09-22 From: "P.Robert Marino" <rob-at-concord-hs.org> Re: [hangout] SuSE Ent9 Server & YOU
  45. 2004-09-22 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] NYLXS Board Meeting Report
  46. 2004-09-22 Ruben Safir <ruben-at-mrbrklyn.com> RE: [hangout] NYLXS Board Meeting Report
  47. 2004-09-22 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Spamassassin Weak Points
  48. 2004-09-22 From: "P.Robert Marino" <rob-at-concord-hs.org> RE: [hangout] SuSE Ent9 Server & YOU
  49. 2004-09-22 From: "P.Robert Marino" <rob-at-concord-hs.org> RE: [hangout] SuSE Ent9 Server & YOU
  50. 2004-09-22 akbar <akbar-at-jaal.org> Re: [hangout] NYLXS Board Meeting Report
  51. 2004-09-22 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] NYLXS Board Meeting Report
  52. 2004-09-22 akbar <akbar-at-jaal.org> RE: [hangout] NYLXS Board Meeting Report
  53. 2004-09-22 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] NYLXS Board Meeting Report
  54. 2004-09-22 akbar <akbar-at-jaal.org> RE: [hangout] NYLXS Board Meeting Report
  55. 2004-09-22 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] NYLXS Board Meeting Report
  56. 2004-09-22 akbar <akbar-at-jaal.org> Re: [hangout] NYLXS Board Meeting Report
  57. 2004-09-22 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  58. 2004-09-22 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] Microsoft software implicated in air traffic shutdo
  59. 2004-09-22 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Microsoft software implicated in air traffic shutdown
  60. 2004-09-22 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Free 96-page report details benefits of Open Source software
  61. 2004-09-22 David Sugar <dyfet-at-ostel.com> Re: [hangout] Nitix Autonomic Linux-based Server Operating System
  62. 2004-09-22 David Sugar <dyfet-at-ostel.com> Re: [hangout] Windows on Warships
  63. 2004-09-22 David Sugar <dyfet-at-ostel.com> Re: [hangout] Paging David Sugar
  64. 2004-09-22 David Sugar <dyfet-at-ostel.com> Re: [hangout] Spamassasin really sucks
  65. 2004-09-22 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Paging David Sugar
  66. 2004-09-22 Ruben Safir <ruben-at-mrbrklyn.com> Re: [hangout] SuSE Ent9 Server & YOU
  67. 2004-09-21 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [Fwd: C3 EXPO Launched - New Computing Event for Corporate & Channel
  68. 2004-09-21 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Sun denies report it is 'selling out' OpenOffice
  69. 2004-09-21 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] OpenOffice: A legal Trojan horse--but for whom?
  70. 2004-09-21 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] NYLXS Board Meeting Report
  71. 2004-09-21 From: "Ruben I Safir - Secretary NYLXS" <ruben-at-mrbrklyn.com> Subject: [hangout] What is wrong with this picture?
  72. 2004-09-21 Billy <billy-at-dadadada.net> Re: [hangout] SuSE Ent9 Server & YOU
  73. 2004-09-21 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] SuSE Ent9 Server & YOU
  74. 2004-09-21 From: "rc" <ray-pub-at-nyc.rr.com> Subject: [hangout] SuSE Ent9 Server & YOU
  75. 2004-09-21 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] Meeting
  76. 2004-09-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] DMCA stuff
  77. 2004-09-20 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] Hang on to your seatbelts.
  78. 2004-09-20 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] Hang on to your seatbelts.
  79. 2004-09-20 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  80. 2004-09-20 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  81. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  82. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  83. 2004-09-20 Ruben Safir <ruben-at-mrbrklyn.com> RE: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  84. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  85. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] VectorLinux 4.3 Has Arrived!
  86. 2004-09-20 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  87. 2004-09-20 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  88. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] L'Shana Tova Tikasayvu (Happy Jewish New Year!)
  89. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] SuSE Tech Kit
  90. 2004-09-20 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] meeting
  91. 2004-09-20 Contrarian <adrba-at-nyct.net> Re: [hangout] meeting
  92. 2004-09-20 Billy <billy-at-dadadada.net> Re: [hangout] Hang on to your seatbelts.
  93. 2004-09-20 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Big Oppurtunity for the Ready Free Software Enterprise Desktop
  94. 2004-09-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Hang on to your seatbelts.
  95. 2004-09-19 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Big Oppurtunity for the Ready Free Software Enterprise Desktop
  96. 2004-09-19 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Sun reports Wall Street sick of Free Software :(
  97. 2004-09-19 Contrarian <adrba-at-nyct.net> Re: [hangout] Sun reports Wall Street sick of Free Software :(
  98. 2004-09-19 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Sun reports Wall Street sick of Free Software :(
  99. 2004-09-19 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] To be young and lost
  100. 2004-09-18 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] To be young and lost
  101. 2004-09-18 Ruben Safir <ruben-at-mrbrklyn.com> RE: [hangout] Sun reports Wall Street sick of Free Software :(
  102. 2004-09-18 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] Sun reports Wall Street sick of Free Software :(
  103. 2004-09-18 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Sun reports Wall Street sick of Free Software :(
  104. 2004-09-18 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Sun reports Wall Street sick of Free Software :(
  105. 2004-09-18 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] MYSQL News
  106. 2004-09-18 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Economist mag
  107. 2004-09-17 From: "rc" <ray-pub-at-nyc.rr.com> Subject: [hangout] SuSE Tech Kit
  108. 2004-09-17 From: "rc" <ray-pub-at-nyc.rr.com> Subject: [hangout] Google & Non-Profit Orgs
  109. 2004-09-17 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Jobs
  110. 2004-09-17 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] More jobs
  111. 2004-09-17 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Jobs
  112. 2004-09-16 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] Meeting
  113. 2004-09-14 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] meeting
  114. 2004-09-14 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] meeting
  115. 2004-09-14 Ruben Safir <ruben-at-mrbrklyn.com> Re: [hangout] meeting
  116. 2004-09-14 Adam Kosmin <akosmin-at-nyc.rr.com> Re: [hangout] Novell sees a 'both-source' future
  117. 2004-09-14 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] meeting
  118. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Novell sees a 'both-source' future
  119. 2004-09-13 Ruben Safir <ruben-at-mrbrklyn.com> Re: [hangout] Novell sees a 'both-source' future
  120. 2004-09-13 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] Novell sees a 'both-source' future
  121. 2004-09-13 Adam Kosmin <akosmin-at-nyc.rr.com> Subject: [hangout] Novell
  122. 2004-09-13 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Novell sees a 'both-source' future
  123. 2004-09-13 Adam Kosmin <akosmin-at-nyc.rr.com> Re: [hangout] Novell sees a 'both-source' future
  124. 2004-09-13 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Novell sees a 'both-source' future
  125. 2004-09-13 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] "Linux Backers to Support Standard"
  126. 2004-09-13 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Malware Writers Using Open-Source Tactics
  127. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Web Site Redesign
  128. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Web Site Redesign
  129. 2004-09-13 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Re:
  130. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Brooklyn Tech Servers
  131. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Re: Educational Institution in Need
  132. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Please Handle this first contact... Thanx
  133. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] I am a man, and you are a woman
  134. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs4.2
  135. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs4.0
  136. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Jobs3.8
  137. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs3.5
  138. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs3.3
  139. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs3.1
  140. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs2.5
  141. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Jobs2
  142. 2004-09-13 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Jobs
  143. 2004-09-12 From: "rc" <ray-pub-at-nyc.rr.com> RE: [hangout] Novell/SuSE offer
  144. 2004-09-11 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] gnomemeeting
  145. 2004-09-11 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Astoria Queens LUG building
  146. 2004-09-11 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Educational Institution in Need
  147. 2004-09-11 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Re: Volunteer needed urgently in Brooklyn
  148. 2004-09-11 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: two dimensional arrays passed to functions
  149. 2004-09-10 Billy <billy-at-dadadada.net> Re: [hangout] Re: two dimensional arrays passed to functions
  150. 2004-09-10 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] INDUCE: Copyright Office Recommended Statutory Language
  151. 2004-09-10 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Linux Business in New York
  152. 2004-09-10 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: two dimensional arrays passed to functions
  153. 2004-09-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Re: [Paranoia-dev] valgrind
  154. 2004-09-10 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Asian Spam - Die Now
  155. 2004-09-09 From: "Ruben" <ruben-at-mrbrklyn.com> Subject: [hangout] Re: two dimensional arrays passed to functions
  156. 2004-09-09 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Subject: [hangout] [DMCA_Discuss] Distributed Search Company Sues RIAA over Patent
  157. 2004-09-09 Billy <billy-at-dadadada.net> Re: [hangout] Re: two dimensional arrays passed to functions
  158. 2004-09-09 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: two dimensional arrays passed to functions
  159. 2004-09-09 Billy <billy-at-dadadada.net> Re: [hangout] Re: two dimensional arrays passed to functions
  160. 2004-09-09 Billy <billy-at-dadadada.net> Re: [hangout] I have no functional gas according to dosemu
  161. 2004-09-09 Billy <billy-at-dadadada.net> Re: [hangout] binutils
  162. 2004-09-09 Billy <billy-at-dadadada.net> Subject: [hangout] DOSEMU for PPC
  163. 2004-09-09 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Novell/SuSE offer
  164. 2004-09-09 From: "Ruben" <ruben-at-mrbrklyn.com> Subject: [hangout] Re: two dimensional arrays passed to functions
  165. 2004-09-09 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Novell/SuSE offer
  166. 2004-09-09 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] C programming: 2d Arrays
  167. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] I have no functional gas according to dosemu
  168. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Binutils disregard previous email
  169. 2004-09-08 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] I have no functional gas according to dosemu
  170. 2004-09-08 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Binutils disregard previous email
  171. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] binutils
  172. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] BSCP
  173. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] Binutil
  174. 2004-09-08 Mike Richardson - NYLXS PRESIDENT <miker-at-mrbrklyn.com> Re: [hangout] Good Morning
  175. 2004-09-08 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Binutil
  176. 2004-09-08 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Binutil
  177. 2004-09-08 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] [reply-c9f4-1808-2f6b114cd7-at-nl.internet.com: Your Linux Today Security Letter for September 8, 2004]
  178. 2004-09-08 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Sybase releases free Express database for Linux
  179. 2004-09-08 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Binutil
  180. 2004-09-08 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Binutil
  181. 2004-09-08 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Binutil
  182. 2004-09-08 Billy <billy-at-dadadada.net> Re: [hangout] Binutil
  183. 2004-09-08 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Good Morning
  184. 2004-09-07 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Whippersnapper whistle-blowers beware
  185. 2004-09-07 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Whistle-blowers form a breed apart
  186. 2004-09-07 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Windows on Warships
  187. 2004-09-07 Michael Richardson <MRichardson-at-abc.state.ny.us> RE: [hangout] Windows on Warships
  188. 2004-09-07 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Windows on Warships
  189. 2004-09-07 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Windows on Warships
  190. 2004-09-07 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Windows on Warships
  191. 2004-09-07 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Printing from Suse 9.1
  192. 2004-09-07 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Printing from Suse 9.1
  193. 2004-09-07 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Printing from Suse 9.1
  194. 2004-09-07 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Printing from Suse 9.1
  195. 2004-09-07 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Printing from Suse 9.1
  196. 2004-09-07 Adam Kosmin <akosmin-at-nyc.rr.com> Subject: [hangout] Windows on Warships
  197. 2004-09-06 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Segfault in mysql_real_escape_string
  198. 2004-09-05 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Registers
  199. 2004-09-05 Billy <billy-at-dadadada.net> Re: [hangout] Registers
  200. 2004-09-05 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] strmov
  201. 2004-09-05 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Registers
  202. 2004-09-05 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  203. 2004-09-05 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] NYLXS Outing.
  204. 2004-09-05 Billy <billy-at-dadadada.net> Re: [hangout] NYLXS Outing.
  205. 2004-09-05 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  206. 2004-09-05 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  207. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  208. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  209. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Re: Help needed with MySQL C API-based client (segfault)
  210. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] What is the Linux equivalent to debug.
  211. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Paging Serge
  212. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  213. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> RE: [hangout] NYLXS Outing.
  214. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] NYLXS Outing.
  215. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  216. 2004-09-04 Ron Guerin <ron-at-vnetworx.net> Re: [hangout] NYLXS Outing.
  217. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] MYSQL and C
  218. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Enterprise Server Suse
  219. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  220. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  221. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  222. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  223. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  224. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  225. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  226. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  227. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  228. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  229. 2004-09-04 Ron Guerin <ron-at-vnetworx.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  230. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  231. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  232. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  233. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  234. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  235. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  236. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  237. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  238. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  239. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  240. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  241. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  242. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  243. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  244. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  245. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  246. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  247. 2004-09-04 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  248. 2004-09-04 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  249. 2004-09-04 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  250. 2004-09-03 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  251. 2004-09-03 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  252. 2004-09-03 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  253. 2004-09-03 Adam Kosmin <akosmin-at-nyc.rr.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  254. 2004-09-03 Ron Guerin <ron-at-vnetworx.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  255. 2004-09-03 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  256. 2004-09-03 From: "Inker, Evan" <EInker-at-gam.com> RE: [hangout] Quite unbeleivable
  257. 2004-09-03 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Subject: [hangout] Quite unbeleivable
  258. 2004-09-02 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Adjusting font sizes and video alignment in Suse 9.1
  259. 2004-09-02 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  260. 2004-09-02 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!? Was RE: [NMLUG] Re:Linux Advocacy FAQ is NOT Linux Advocacy Maxim (RobertDelahunt) (Daniel Lark)
  261. 2004-09-02 Billy <billy-at-dadadada.net> Re: [hangout] Re: Advocacy vs. Zealotry vs. Who Cares?!?
  262. 2004-09-02 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Re: [hangout] Assembly
  263. 2004-09-02 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Kerberos Holes Could Bring Serious Exploits (3 Articles Worth Rea
  264. 2004-09-02 Billy <billy-at-dadadada.net> Re: [hangout] Assembly
  265. 2004-09-02 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Assembly
  266. 2004-09-01 Billy <billy-at-dadadada.net> Re: [hangout] Assembly
  267. 2004-09-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [hangout] Weekend Activities
  268. 2004-09-01 Steve Milo <slavik914-at-mrbrklyn.com> Subject: [hangout] Re: [NMLUG] Re: Linux Advocacy FAQ is NOT Linux Advocacy Maxim
  269. 2004-09-01 Steve Milo <slavik914-at-mrbrklyn.com> Subject: [hangout] freedom-it
  270. 2004-09-01 Steve Milo <slavik914-at-mrbrklyn.com> Re: [hangout] Assembly
  271. 2004-09-01 Billy <billy-at-dadadada.net> Re: [hangout] Assembly
  272. 2004-09-01 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Xybernaut adds Linux as an OS option
  273. 2004-09-01 From: "Steve Milo" <slavik914-at-mrbrklyn.com> Subject: [hangout] Assembly
  274. 2004-09-01 Billy <billy-at-dadadada.net> Re: [hangout] Assembly
  275. 2004-09-01 Billy <billy-at-dadadada.net> Re: [hangout] Assembly
  276. 2004-09-01 From: "Inker, Evan" <EInker-at-gam.com> Subject: [hangout] Oklahoma non-profit finds open source OK
  277. 2004-09-01 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Assembly
  278. 2004-09-01 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Assembly
  279. 2004-09-01 Ruben Safir Secretary NYLXS <ruben-at-mrbrklyn.com> Re: [hangout] Assembly

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!