public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2 to 3??
Date: Wed, 18 Jul 2007 11:33:20 -0500	[thread overview]
Message-ID: <200707181133.20823.bss03@volumehost.net> (raw)
In-Reply-To: <D75F362B-E460-4392-8FCA-7DE6C889F9ED@stellar.eclipse.co.uk>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

On Wednesday 18 July 2007, Stroller <stroller@stellar.eclipse.co.uk> wrote 
about 'Re: [gentoo-user] 2 to 3??':
> However, this is not the point.
>
> The point is that Tivo SOLD people hardware

This is the salient point for me, too.  If hardware was still owned by TiVo 
(in reality, not just in name) I'd have no problem with them deciding what 
can run on it and taking steps to prevent tampering.

I'm not sure Stallman would agree with me -- users may or may not own the 
device their software runs on, and Stallman is all about users.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-18 16:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 17:38 [gentoo-user] 2 to 3?? burlingk
2007-07-17 17:27 ` Boyd Stephen Smith Jr.
2007-07-18 12:38   ` Alan McKinnon
2007-07-18 14:13     ` Stroller
2007-07-18 16:15     ` Boyd Stephen Smith Jr.
2007-07-18 13:48 ` Stroller
2007-07-18 16:33   ` Boyd Stephen Smith Jr. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-19 14:37 burlingk
2007-07-19  6:13 burlingk
2007-07-19  5:59 ` Boyd Stephen Smith Jr.
2007-07-19  5:54 burlingk
2007-07-18 11:07 burlingk
2007-07-18 12:29 ` Dan Cowsill
2007-07-18  4:26 burlingk
2007-07-18  4:18 burlingk
2007-07-17 17:57 burlingk
2007-07-18 13:51 ` Stroller
2007-07-17 12:12 burlingk
2007-07-17 11:29 ` Abraham Marín Pérez
2007-07-17 10:14 burlingk
2007-07-17 10:42 ` Abraham Marín Pérez
2007-07-17 11:01 ` Graham Murray
2007-07-17 12:48   ` Stroller
2007-07-17 16:19     ` Volker Armin Hemmann
2007-07-18 13:13       ` Stroller
2007-07-18 17:40         ` Volker Armin Hemmann
2007-07-18 18:10           ` Boyd Stephen Smith Jr.
2007-07-18 22:34           ` Stroller
2007-07-18 23:48             ` Volker Armin Hemmann
2007-07-19  0:41               ` Boyd Stephen Smith Jr.
2007-07-19  2:10                 ` Stroller
2007-07-19  1:58               ` Stroller
2007-07-17 17:14 ` Boyd Stephen Smith Jr.
2007-07-17 19:29   ` Mike Edenfield
2007-07-16  0:52 burlingk
2007-07-16 12:15 ` Mark Shields
2007-07-16 21:53   ` Jerry McBride
2007-07-17  1:26     ` Volker Armin Hemmann
2007-07-17  1:59       ` Boyd Stephen Smith Jr.
2007-07-17  1:26   ` Volker Armin Hemmann
2007-07-17  2:08     ` Henk Boom
2007-07-13 22:11 Jerry McBride
2007-07-13 22:27 ` Bo Ørsted Andresen
2007-07-18  9:28 ` b.n.
2007-07-18 16:23   ` Boyd Stephen Smith Jr.

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=200707181133.20823.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox