[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy hardware-software-boundary.html
From: |
Richard M. Stallman |
Subject: |
www/philosophy hardware-software-boundary.html |
Date: |
Fri, 20 Mar 2015 20:59:12 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Richard M. Stallman <rms> 15/03/20 20:59:12
Modified files:
philosophy : hardware-software-boundary.html
Log message:
Rewrite text about gray area.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/hardware-software-boundary.html?cvsroot=www&r1=1.2&r2=1.3
Patches:
Index: hardware-software-boundary.html
===================================================================
RCS file: /web/www/www/philosophy/hardware-software-boundary.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- hardware-software-boundary.html 10 Mar 2015 14:57:56 -0000 1.2
+++ hardware-software-boundary.html 20 Mar 2015 20:59:11 -0000 1.3
@@ -13,9 +13,9 @@
right way to make the distinction because it relates to the practical
consequences.</p>
-<p>There is a gray area between hardware and software that contains
+<p>Between hardware and software there is a gray area consisting of
firmware that <em>can</em> be upgraded or replaced, but is not meant
-ever to be upgraded or replaced once the product is sold. In
+to be upgraded or replaced once the product is sold. In
conceptual terms, the gray area is rather narrow. In practice, it is
important because many products fall in it. We can treat that
firmware as hardware with a small stretch.</p>
@@ -106,7 +106,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2015/03/10 14:57:56 $
+$Date: 2015/03/20 20:59:11 $
<!-- timestamp end -->
</p>
</div>