Author: Ye Weibin MSN: fritz_yea@hotmail.comCopyright (C) Free Software Library.Org (http://yea.xiloo.com) in accordance with article GNU Free Document Lience released, anyone can copy this article intact, reprint But please keep this statement. The author is not responsible for any result caused by this article.
0, the opening ceremony This article is the first manuscript of my life, the topic is called "Slackware Batter". But after the investment, the stone sea, this is also among my expectations. After all, this is my first writing articles, the experience is insufficient, and there are many nonsense. But since writing, I can't bear to throw it back to the waste paper, and the sure is posted here, let the masters directly criticize. The first-hand opinion obtained can also learn, make me progress (hey, the original manuscript is not so good!). The title of the article I gave it, because I am still using RedHat 8, including this article, is written under the Emacs of RH8. I don't know if it issued a question or I really won't use it, I hit the wall around Slackware 9. Unable to use ordinary users (Shutdown, Halt, Reboot, etc. I don't have enough permissions), I can't install the RPM package, the compilation and installation source code package is not good (always I don't have enough permissions, I am root!), No way, I have to transfer RedHat to avoid the above problems. For truth from facts, I must also change the name and part of the original article, and what I said, basically in the GNU / Linux environment, which is not for a specific system.
1. Prepare a one, a better Linux partition principle is: Separate a / (main), one / swap (main), one / home, one / usr / local (logic). My hard disk partitions are as follows: / dev / hda1 primer fat32 msdos C: / 1GB / DEV / HDA2 PRIMER / DEV / HDA5 Logical FAT32 MSDOS D: / 3.9GB / DEV / HDA6 Logical EXT2 Linux / Home 1.5GB / dev / hda3 primer Ext2 Linux / 2.7GB / dev / hda4 primer Linux swap Linux / swap 300MB suggests that you use the PQ MAGIC partition tool, which is neither damaged partition and is convenient.
Second, install me is using the red hat 8, download the disc image you engraved. Install the graphical interface, the process is relatively smooth. RH installation has always been relatively simple, and the various information is also very rich, I will not go out. I chose packages installed for basic systems, x, gnome, development tools, network tools, text editing, etc. This puts the foundation for future use.
Third, configure me to talk about my machine: Toshiba Satellite 2655xDVD (Notebook): CPU: CPU: Celron 466 Ram: 128MB HD: 10GB IDE FD: 1.44MB CD-ROM: 8XDVD Modem: Lucent WinModem V.90 Lancard: Cardbus 10 / 100 Fast Ethernet Adapter II SoundCard: ES1978 Maestro 2e VideoCard: Trident Cyber9525XDVD 2MB Ram PCMCIA: Type II X2 From the installation process, I have been well supported in addition to "inner cat", all hardware is well supported . Redhat has made great progress at this point. Through multiple installations, there is a need to explain it. I. Delive points of each hardware. My hard drive is / dev / hda, the optical drive is / dev / cdrom, is actually a symbolic link, pointing to / dev / hdc. The hard disk is basically not wrong, but if your optical drive is not installed, you can check if the link / dev / cdrom is pointing to where it is your CD-ROM. If not, just modify the link. At the beginning I installed Slackware, the optical drive was inexplicably pointing to / dev / sdc0, helping me to find a half-day optical drive. Modify the link Use the following command: #RM / dev / cdrom file: // Remove the old link #LN -S / dev / hdc / dev / cdrom file: // Establish the correct link II. Multi-system boot. If you have to be like me, use a dual system, so it will inevitably involve the problem of system boot. I use LILO to boot the system and put it in MBR. Original RH's default boot program is GRUB, but I won't configure grub, and I got an unexpected gain when I installed SLACKWARE, and I can expand the screen's display, I think this is also very "local" users. Useful features. The new Linux kernel supports the extended console mode, which can extend the console from the original 640x480x256 color mode to 1024x768x64k color mode, simply, expand the display amount of 80 characters per row, expand the display range of the screen. So my notebook can be full screen to display the console, not the original small window (it seems that many notebooks have this problem, showing text mode, always small screen, watching very uncomfortable.) Modify the automatic generation of / ETC /lilo.conf file (I will give my lilo.conf). # ------------------------------------------------------- --------------------- # prompter = 50DEFAULT = WIN <--- Note Here, this is my own, so that the startup defaults to Win. After waiting for 5 seconds, I will launch Windows directly. Boot = / dev / hdamap = / boot / mapinstall = / boot / boot.bmessage = / boot / messageelba32vga = 790 <--- and here, this is to expand the display range, to 1024x768x64k
Image = / boot / vmlinuz-2.4.18-14 label = linux initrd = / boot / initrd-2.4.18-14.img read-only append = "root = label = /" 中 = / dev / hda1 optional label = WIN # ----------------------------- My Lilo Configuration (End) ------------- ------------------------ #
The above VGA = 790 is that I have copied from the slonware of Slackware. I checked the LILO man page, I only wrote VGA = Normal, or specified the number of characters of the display, the number of characters, but did not exemplify. When I installed Slackware, it reminds me that the new kernel supports console extention, and the result is obtained below. This makes setting VGA very intuitive, everyone may wish to write it down.
# VESA framebuffer console @ 1024x768x32k # Normal VGA console # vga = normal # VESA framebuffer console @ 1024x768x64k # vga = 791 # VESA framebuffer console @ 1024x768x32k # vga = 790 # VESA framebuffer console @ 1024x768x256 # vga = 773 # VESA framebuffer console @ 800x600x64k # vga = 788 # VESA framebuffer console @ 800x600x32k # vga = 787 # VESA framebuffer console @ 800x600x256 # vga = 771 # VESA framebuffer console @ 640x480x64k # vga = 785 # VESA framebuffer console @ 640x480x32k # vga = 784 # VESA framebuffer console @ 640x480x256 # vga = 769
