All of lore.kernel.org
 help / color / mirror / Atom feed
From: joy merwin monteiro <joy.merwin@gmail.com>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: filtering .mp3 packets
Date: Sat, 30 Apr 2005 05:09:37 +0530	[thread overview]
Message-ID: <4b0d6e0d050429163925e0450e@mail.gmail.com> (raw)
In-Reply-To: <427257F7.7040800@comarre.com>

> Whether this is a good solution or not depends on what the perceived
> problem is.
> 
> If the issue is file sharers tying up bandwidth to the Internet, this is
> an excellent approach. It will limit all heavy users indiscriminately,
> though, so someone who (say) does a network-based upgrade of his or her
> Linux host (an "apt-get upgrade" in Debian terms, or the equivalent for
> other distros) or downloads ISO images of Linux-distro CDs will be
> limited in the same way as someone doing a lot of music downloads.

IMO, a local campus LAN with limited bandwidth, a net upgrade of
your system is as bad as p2p dowloading....... as you have mentioned,
if bandwidth
saving is the only issue, some legit computers can be allocated more b/w for 
such legitimate reasons.
> 
> If the issue is preventing use of the Internet connection to download
> unauthorized copies of copyrighted materials, then this approach is
> probably not sufficiently targeted to accomplish what the original
> poster requested. It has the "false positive" problem in spades.
> 
Totally agree, but if this problem had a ready solution, Linux based
or otherwise,
the RIAA would have made it mandatory by now :-)

> If the issue is inhibiting on-LAN exchanges of unauthorized copies of
> copyrighted materials ... well in that case, this entire discussion's
> focus on solutions at the router level is completely misplaced. If that
> is the perceived problem (in a college setting, I can easily imagine it
> being so, especially of the LAN provides service to dorm rooms), the
> solution needs to involve a heavy dose of on-LAN traffic sniffing. Even
> talking about that approach requires less abstraction from a particular
> LAN implementation then we have had here so far.
>
 
From my experience (being presently in college), I would prefer to burn a
CD with 700 MB of songs and distribute it to all the people who need it rather
than trying to send it over a LAN..... people who want to do it 
_will_ find a way to do it......

-- 
<ed__> riel: if it were a vax, gcc would probably be an opcode

	- excerpt from #kernelnewbies
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      reply	other threads:[~2005-04-29 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 11:27 filtering .mp3 packets William Stanard
2005-04-25 16:56 ` Ray Olszewski
2005-04-26 11:36 ` John T. Williams
2005-04-27 14:15   ` J.
2005-04-27 15:22     ` simon
2005-04-27 19:51       ` J.
2005-04-27 22:57         ` John T. Williams
2005-04-28  0:39           ` Ray Olszewski
2005-04-29  3:05             ` joy merwin monteiro
2005-04-29 11:43               ` Stephen Ray
2005-04-29 15:24                 ` joy merwin monteiro
2005-04-29 15:51                   ` Ray Olszewski
2005-04-29 23:39                     ` joy merwin monteiro [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b0d6e0d050429163925e0450e@mail.gmail.com \
    --to=joy.merwin@gmail.com \
    --cc=joy_mm@ieee.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.