diff options
author | Karsten Merker <merker@debian.org> | 2012-09-06 20:49:06 +0000 |
---|---|---|
committer | Karsten Merker <merker@debian.org> | 2012-09-06 20:49:06 +0000 |
commit | a35bbf043d05d833ada0169a8908c449db1db4c0 (patch) | |
tree | efb9e5fcddcbb5668d44e4a639ed2e8ece0a4b2f /en/hardware | |
parent | 260cfcc5c744d5d6f59ae97535338f44d611a13d (diff) | |
download | installation-guide-a35bbf043d05d833ada0169a8908c449db1db4c0.zip |
Installation-guide cleanup
* Various small removals / updates / amendments in chapter 3,
most of them concerning outdated information.
* Extended the "Devices Requiring Firmware" section.
* Rewrote large parts of the "Avoid Proprietary or Closed Hardware"
section.
* Rewrote the "Hardware Compatibility" section.
* Amended the "Network Settings" section.
* Rewrote the "Pre-Partitioning for Multi-Boot Systems" section
to bring it up to date with the current d-i features and make it
easier to read for beginners.
* Rewrote the "Pre-Installation Hardware and Operating System Setup"
section to bring it up to date for modern hardware.
Diffstat (limited to 'en/hardware')
-rw-r--r-- | en/hardware/buying-hardware.xml | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/en/hardware/buying-hardware.xml b/en/hardware/buying-hardware.xml index 48c20e4c7..a6dd3b144 100644 --- a/en/hardware/buying-hardware.xml +++ b/en/hardware/buying-hardware.xml @@ -36,11 +36,9 @@ vendors. Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from -releasing the &arch-kernel; source code. - -</para><para> - -Since we haven't been granted access to the documentation on these +releasing the driver's source code, which is one of the central +elements of free software. +Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;. </para><para> @@ -61,7 +59,8 @@ In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which -only understand proprietary control commands and either cannot be used at +only understand proprietary control commands for which no usable +documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver. |