📄 00000062.htm
字号:
<BR>
<BR>Okay, you've sold me on the idea. What next?
<BR>
<BR>The first thing you will need to do is pick a distribution. Linux is packaged <BR>as collections of programs, applications, utilities, and the
<BR>operating system, by different people and vendors. These are called <BR>distributions. There are many, fine distributions out there, and
<BR>choosing the "right" one is a nebulous process. This is somewhat analogous to <BR>picking the "best" vacation spot, or the "best" outfit
<BR>to wear.
<BR>
<BR>I will be discussing the Slackware 3.5, and RedHat 5.1, as these are the ones <BR>I am familiar with. Many of the descriptions and
<BR>configuration options, most notably the autoprobing of PCI devices, and <BR>support for many newer video cards, are applicable
<BR>ONLY to these distributions. All my comments and recommendations are just <BR>that - comments and recommendations. Your
<BR>preferences may be entirely different.
<BR>
<BR>Slackware 3.5
<BR>
<BR>The first distribution I ever used, and still my favorite. It has the option <BR>for either a Command Line Interface (CLI) install, or a
<BR>Graphical User Interface (GUI) install. Uses Tarballs, or .tgz package <BR>format. I like this because I am not "forced" to install X just
<BR>to use my system like some of the other distributions ( see below.) I am also <BR>given more control over what does and does not get
<BR>installed. (Upgrade path is not too good.) Best for people who want to really <BR>learn about how the system works, and like installing
<BR>and compiling their own software. A full install will eat up ~400MB of disk <BR>space.
<BR>
<BR>RedHat 5.1
<BR>
<BR>This is the current "darling" of the commercial side of the Linux community. <BR>Probably the easiest to install. Forces the installation
<BR>of the X window system, whether you want it or not. Uses the RPM package <BR>format to ensure all packages and programs are
<BR>installed correctly (sort of.) Upgrade path is good. Currently has the lion's <BR>share of the media attention, and thus, application
<BR>support. This is the one I recommend for people who want a working system <BR>quickly, and are less concerned about the internal
<BR>workings of the Operating System. A full install will eat up ~600MB of disk <BR>space.
<BR>
<BR>I had originally intended to do an in-depth comparison of the various <BR>distributions, but the August issue of the Linux Journal just
<BR>arrived in my mailbox today, and I see that Phil has beat me to it. I <BR>respectfully disagree with regard to the Caldera Distribution. I
<BR>am overwhelmed by it's cost, and underwhelmed by it's performance. Other than <BR>that, I would suggest you refer to his article for a
<BR>more in-depth comparison. He has done an outstanding job, much better than I <BR>could have ever done.
<BR>
<BR>
<BR>
<BR>How do I get the software?
<BR>
<BR>Here you have several options. All the distributions I mention are freely <BR>available on the Internet for download. Additionally,
<BR>RedHat, and Slackware are available for purchase, either directly from the <BR>manufacturers, or through third parties. Finally, some
<BR>or all of them are often bundled with books on Linux or can be had at your <BR>local Linux User's Group's Install Party, an event
<BR>where people bring in their computers and the hosts at your Linux users Group <BR>will install the software for you.
<BR>
<BR>IMPORTANT NOTE: While it is possible to install some of these distributions <BR>using FTP or NFS, I strongly urge you to acquire a
<BR>CD-ROM for your first installation. See the resources section at the end of <BR>this document for vendors, or check your local book
<BR>store.
<BR>
<BR>While an Install Party is probably the easiest method to get your system up <BR>and running, You will get more out of it by doing the
<BR>installation yourself. Messing up, and doing it yourself is the best way to <BR>learn.
<BR>
<BR>
<BR>
<BR>What sort of planning should I do beforehand?
<BR>
<BR>Excellent question. Here are some things to consider:
<BR>
<BR>While it is possible and feasible to have multiple operating systems residing <BR>on one system, I recommend using a separate machine
<BR>if possible, or at least a separate disk or disks on your machine just for <BR>Linux.
<BR>
<BR>This will give you the confidence to bang away at it, install multiple times, <BR>and decrease the chance of harming your primary OS or
<BR>data. Also, in later installments, I will show you how to make this machine <BR>do all kinds of neat tricks, like serve up your Internet
<BR>connection, store files and applications, even become the starting point for <BR>your own home network.
<BR>
<BR>
<BR>
<BR>I'm not rich, where can I find a cheap machine like you mention?
<BR>
<BR>Check around in the paper, your local Linux user group, your place of <BR>employment or even your local community college for one
<BR>of those "old" machines. They can often be had at little or no cost.
<BR>
<BR>What we are aiming for here is maximizing your chances for a successful <BR>installation, there will be plenty of time for you to learn
<BR>the more esoteric methods as your Unix skills increase.
<BR>
<BR>If at all possible try to get a separate machine, preferably with two Hard <BR>Disk Drives, and an ATAPI compliant CD-ROM.
<BR>
<BR>
<BR>
<BR>That sounds like a lot of trouble. Can't I just try it out without all that <BR>extra stuff?
<BR>
<BR>If you absolutely must disregard my warnings, and intend to try out Linux on <BR>your primary machine, BACKUP ANYTHING
<BR>YOU CAN NOT AFFORD TO LOSE ONTO FLOPPY DISK, TAPE, OR WHATEVER BACKUP DEVICE <BR>YOU
<BR>PRESENTLY USE. IF YOU DON'T HAVE ONE, PUT THIS DOWN AND GO GET ONE! YOU HAVE <BR>BEEN WARNED.
<BR>Consider the Slackware distribution. It offers the option of running directly <BR>off of the CD-ROM.
<BR>
<BR>
<BR>
<BR>Okay, I have the machine or extra disk(s), what next?
<BR>
<BR>If you have not acquired a separate machine, refer to the warning above. <BR>BACKUP ANYTHING YOU CANNOT AFFORD
<BR>TO LOSE.
<BR>
<BR>The first thing you will need to do is create your boot disk, and in some <BR>cases, a root or supplemental disk.
<BR>
<BR>If you purchased the commercial distribution of RedHat, the required disks <BR>should already be included. The commercial version of
<BR>Slackware should be bootable directly from the CD-ROM on newer systems.
<BR>
<BR>If you obtained the software bundled with a book, you will probably need to <BR>create the disk or disks yourself.
<BR>
<BR>You will need one or two DOS formatted disks for this.
<BR>
<BR>What boot image you need will depend on which distribution you are <BR>installing.
<BR>
<BR>For RedHat, look for the /images directory, which should contain two files <BR>named boot.img and supp.img. Normally only the
<BR>boot.img disk will be required.
<BR>
<BR>For Slackware, look for a directory called /bootdsks.144, and another called <BR>/rootdsks. Unless you have something other than IDE
<BR>devices in your machine, the bare.i image is the one you will be looking for <BR>as your boot disk. In the rootdsks directory, you will
<BR>need the color.gz image for your root disk.
<BR>
<BR>The method used for creating your boot and/or root disks will depend on <BR>whether you are using a Linux (or Unix) machine, or a
<BR>DOS based machine.
<BR>
<BR>If you are on a DOS based machine, I.E. Windows 3.x, Windows 95, Windows 98 <BR>or Windows NT, you will need to use
<BR>RAWRITE.EXE to create your images. This program should be included either in <BR>the same place as the images we just discussed,
<BR>or under an /install, or /dosutils directory in some cases.
<BR>
<BR>You will need to open a command prompt (sometimes called a DOS box) on your <BR>machine, or exit windows to get to the
<BR>command prompt.
<BR>
<BR>Then type: RAWRITE <enter> You will be asked for the source file name:bare.i <BR><enter>
<BR>
<BR>You will next be asked for your target drive: A: <enter>
<BR>
<BR>If the program errors out, and complains about "Attempting to DMA across 64k <BR>boundary," FTP to sunsite.unc.edu, then cd to:
<BR>
<BR>/pub/Linux/distributions/redhat/redhat-5.1/i386/dosutils/
<BR>
<BR>And retrieve the version of RAWRITE there. It will be smaller than the one <BR>you were using (~14k,) and the problem should go
<BR>away. As I recall this is only an issue on NT and possibly Windows 98 boxes. <BR>
<BR>
<BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -