mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
9df77e91b8
commit
d6a0887a1d
|
|
@ -25,9 +25,18 @@
|
|||
</copyright>
|
||||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>5.5</revnumber>
|
||||
<date>2001-07-11</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
PnP cards are no longer a problem.
|
||||
</revremark>
|
||||
</revision>
|
||||
|
||||
<revision>
|
||||
<revnumber>5.4</revnumber>
|
||||
<date>14 June 2001</date>
|
||||
<date>2001-06-14</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Added link to Post-installation HOWTO.
|
||||
|
|
@ -36,7 +45,7 @@
|
|||
|
||||
<revision>
|
||||
<revnumber>5.3</revnumber>
|
||||
<date>9 March 2001</date>
|
||||
<date>2001-03-9</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Fixes for various links.
|
||||
|
|
@ -45,7 +54,7 @@
|
|||
|
||||
<revision>
|
||||
<revnumber>5.2</revnumber>
|
||||
<date>22 February 2001</date>
|
||||
<date>2001-02-22</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
LDP Styleguide markup fixes.
|
||||
|
|
@ -54,7 +63,7 @@
|
|||
|
||||
<revision>
|
||||
<revnumber>5.1</revnumber>
|
||||
<date>29 January 2001</date>
|
||||
<date>2001-01-29</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Minor corrections for the post-2.1 world.
|
||||
|
|
@ -63,7 +72,7 @@
|
|||
|
||||
<revision>
|
||||
<revnumber>5.0</revnumber>
|
||||
<date>21 August 2000</date>
|
||||
<date>2000-07-21</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
First DocBook version.
|
||||
|
|
@ -124,7 +133,7 @@ information than is contained here. You can browse it, or download a copy,
|
|||
from the LDP home page.</para>
|
||||
|
||||
<para>Finally, there is a rather technical <ulink
|
||||
url="http://www.nondot.org/sabre/os/S1Booting/x86Bootstrapping.html">Guide
|
||||
url="http://www.nondot.org/sabre/os/files/Booting/x86Bootstrapping.html">Guide
|
||||
to x86 Bootstrapping</ulink>. This document is NetBSD- rather than
|
||||
Linux-oriented, but contains useful material on disk configuration and boot
|
||||
managers for multi-OS setups.</para>
|
||||
|
|
@ -238,26 +247,13 @@ Linux SCSI-HOWTO contains more information on SCSI. If you are assembling
|
|||
a system from scratch to run Linux, the small additional cost of SCSI is
|
||||
well worth it for the extra performance and reliability it brings.</para>
|
||||
|
||||
<para>You will need a 3.5" floppy drive<indexterm><primary>floppy
|
||||
drive</primary></indexterm>. While 5.25" floppies are supported under
|
||||
Linux, they are little-enough used that you should not count on disk images
|
||||
necessarily fitting on them. (A stripped-down Linux can actually run on a
|
||||
single floppy, but that's only useful for installation and certain
|
||||
troubleshooting tasks.)</para>
|
||||
|
||||
<para>You also need an MDA<indexterm><primary>MDA</primary></indexterm>,
|
||||
Hercules, CGA<indexterm><primary>CGA</primary></indexterm>,
|
||||
EGA<indexterm><primary>EGA</primary></indexterm>,
|
||||
VGA<indexterm><primary>VGA</primary></indexterm>, or Super
|
||||
VGA<indexterm><primary>Super VGA</primary></indexterm> video card and
|
||||
monitor. In general, if your video card and monitor work under MS-DOS then
|
||||
it should work under Linux. However, if you wish to run the X window
|
||||
system, there are other restrictions on the supported video hardware. The
|
||||
<ulink url="&howto;XFree86-HOWTO.html">Linux XFree86-HOWTO</ulink>,
|
||||
contains more information about running X and its requirements.</para>
|
||||
|
||||
<para>You'll want a CD-ROM<indexterm><primary>CD-ROM</primary></indexterm>
|
||||
drive. If it's ATAPI<indexterm><primary>ATAPI</primary></indexterm>,
|
||||
drive; effectively all Linux distributions are now CD-ROM based. If your
|
||||
machine was built in 1998 or later, you should be able to actually boot
|
||||
your Linux's installer right off the CD-ROM without using a boot
|
||||
floppy.</para>
|
||||
|
||||
<para>If your CD-ROM is ATAPI<indexterm><primary>ATAPI</primary></indexterm>,
|
||||
SCSI<indexterm><primary>SCSI</primary></indexterm>, or true
|
||||
IDE<indexterm><primary>IDE</primary></indexterm> you should have no problem
|
||||
making it work (but watch for cheap drives advertising "IDE" interfaces
|
||||
|
|
@ -269,10 +265,25 @@ at all. If you're in doubt, consult the <ulink
|
|||
url="&howto;CDROM-HOWTO.html">Linux CD-ROM HOWTO</ulink> for a list and
|
||||
details of supported hardware.</para>
|
||||
|
||||
<para>So-called "Plug'n'Play" jumperless cards can be a problem. Support
|
||||
for these is under active development, but not there yet in the 2.0.25
|
||||
kernel. Fortunately this is only likely to be a problem with sound or
|
||||
Ethernet cards.</para>
|
||||
<para>If your CD-ROM isn't in your machine's boot sequence, you will need a
|
||||
3.5" floppy drive<indexterm><primary>floppy
|
||||
drive</primary></indexterm>. While 5.25" floppies are supported under
|
||||
Linux, they are little-enough used that you should not count on disk images
|
||||
necessarily fitting on them. (A stripped-down Linux can actually run on a
|
||||
single floppy, but that's only useful for installation and certain
|
||||
troubleshooting tasks.)</para>
|
||||
|
||||
<para>You also need an MDA<indexterm><primary>MDA</primary></indexterm>,
|
||||
Hercules, CGA<indexterm><primary>CGA</primary></indexterm>,
|
||||
EGA<indexterm><primary>EGA</primary></indexterm>,
|
||||
VGA<indexterm><primary>VGA</primary></indexterm>, or Super
|
||||
VGA<indexterm><primary>Super VGA</primary></indexterm> video card and
|
||||
monitor. In general, if your video card and monitor work under MS-DOS or
|
||||
Windows then they should work under Linux. However, if you wish to run the
|
||||
X window system, there are other restrictions on the supported video
|
||||
hardware. The <ulink url="&howto;XFree86-HOWTO.html">Linux
|
||||
XFree86-HOWTO</ulink>, contains more information about running X and its
|
||||
requirements.</para>
|
||||
|
||||
<para>If you're running on a box that uses one of the Motorola 68K
|
||||
processors (including Amiga<indexterm><primary>Amiga</primary></indexterm>,
|
||||
|
|
|
|||
|
|
@ -18,9 +18,21 @@
|
|||
</author>
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>1.19</revnumber>
|
||||
<date>14 June 2001</date>
|
||||
<revnumber>1.20</revnumber>
|
||||
<date>2001-06-14</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Removed "Practical Unix Security"; it's five years old and
|
||||
the material is now covered better by other books.
|
||||
</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>1.19</revnumber>
|
||||
<date>2001-06-14</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Added Ross Anderson's "Security Engineering". Corected ISBNs.
|
||||
</revremark>
|
||||
</revision>
|
||||
</revhistory>
|
||||
<copyright>
|
||||
|
|
@ -309,27 +321,6 @@ accepted.)</para>
|
|||
</abstract>
|
||||
</biblioentry>
|
||||
|
||||
<biblioentry>
|
||||
<title>Practical Unix and Internet Security</title>
|
||||
<edition>Second Edition</edition>
|
||||
<authorgroup>
|
||||
<author><firstname>Simpson</firstname><surname>Garfinkel</surname></author>
|
||||
<author><firstname>Gene</firstname><surname>Spafford</surname></author>
|
||||
</authorgroup>
|
||||
<copyright><year>1996</year></copyright>
|
||||
<isbn>ISBN 1-56592-148-8</isbn>
|
||||
<publisher><publishername>O'Reilly & Associates</publishername></publisher>
|
||||
<abstract>
|
||||
<para>Ronald P. Miller: "Some overlap with Essential System Admin.,
|
||||
but all in all a solid book on security, especially for those
|
||||
aspiring to allow multiple-user, dial-up/net access to their Linux
|
||||
boxes."</para>
|
||||
|
||||
<para><ulink url="http://www.oreilly.com/catalog/puis/">
|
||||
Order here.</ulink></para>
|
||||
</abstract>
|
||||
</biblioentry>
|
||||
|
||||
</bibliodiv>
|
||||
<bibliodiv><title>Books on Shell, Script, and Web Programming</title>
|
||||
|
||||
|
|
|
|||
|
|
@ -24,9 +24,17 @@
|
|||
</copyright>
|
||||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>3.2</revnumber>
|
||||
<date>2001-07-11</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
Note about not relying on proprietary components.
|
||||
</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>3.1</revnumber>
|
||||
<date>22 February 2001</date>
|
||||
<date>2001-02-22</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
LDP Styleguide fixes.
|
||||
|
|
@ -34,7 +42,7 @@
|
|||
</revision>
|
||||
<revision>
|
||||
<revnumber>3.0</revnumber>
|
||||
<date>12 August 2000</date>
|
||||
<date>2000-08-12</date>
|
||||
<authorinitials>esr</authorinitials>
|
||||
<revremark>
|
||||
First DocBook version. Advice on SourceForge and a major section
|
||||
|
|
@ -396,6 +404,13 @@ implementations are still scratchy and poorly integrated with Linux.
|
|||
Java is still a bleeding-edge choice, though one likely to become more
|
||||
popular as it matures.</para>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="proprietary"><title>Don't rely on proprietary code</title>
|
||||
|
||||
<para>Don't rely on proprietary languages, libraries, or other code.
|
||||
In the open-source community this is considered rude. Open-source
|
||||
developers don't trust what they can't see the source code of.</para>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="cport"><title>Follow good C portability practices</title>
|
||||
|
||||
|
|
@ -424,6 +439,11 @@ errors at least once before each release. This catches a surprising
|
|||
number of errors. For real thoroughness, compile with -pedantic as
|
||||
well.</para>
|
||||
|
||||
<para>For Python projects, the
|
||||
<ulink url="http://sourceforge.net/projects/pychecker">PyChecker</ulink>
|
||||
program can be a useful check. It's not out of beta yet, but nevertheless
|
||||
often catches nontrivial errors.</para>
|
||||
|
||||
<para>If you're writing Perl, check your code with perl -c (and maybe
|
||||
-T, if applicable). Use perl -w and 'use strict' religiously. (See
|
||||
the Perl documentation for discussion.)</para>
|
||||
|
|
@ -557,7 +577,7 @@ the project</para></listitem>
|
|||
|
||||
<para>Note the overall convention that filenames with all-caps names are
|
||||
human-readable metainformation about the package, rather than build
|
||||
components.</para>
|
||||
components (TAGS is an exception).</para>
|
||||
|
||||
<para>Having a FAQ can save you a lot of grief. When a question about the
|
||||
project comes up often, put it in the FAQ; then direct users to read the
|
||||
|
|
@ -687,7 +707,7 @@ of interest across the entire collection.</para>
|
|||
<listitem>
|
||||
<para>The most most common format, inherited from Unix, a primitive form of
|
||||
presentation markup. The <command>man(1)</command> command provides a
|
||||
pager and stone-age search facility. No support for images or hyperlinks
|
||||
pager and a stone-age search facility. No support for images or hyperlinks
|
||||
or indexing. Renders to Postscript for printing fairly well. Doesn't
|
||||
render to HTML at all well (essentially as flat text). Tools are
|
||||
preinstalled on all Linux systems.</para>
|
||||
|
|
@ -910,7 +930,7 @@ the Noosphere</ulink>.</para>
|
|||
|
||||
<para>These papers are not the last word on open-source development. But they
|
||||
were the first serious analyses to be written, and have yet to be
|
||||
superseded (though the author hopes they will be somesday).</para>
|
||||
superseded (though the author hopes they will be someday).</para>
|
||||
|
||||
</sect1>
|
||||
</article>
|
||||
|
|
|
|||
Loading…
Reference in New Issue