📄 00000007.htm
字号:
still ahead :^) ] <BR> <BR> Here's a workaround you can use to install anyway: <BR> <BR> 1. Start tty12 or tty144 using one of the bootkernel disks. <BR> 2. Make and format partitions for Linux. <BR> 3. Mount the target partitions under /mnt. <BR> 4. Type "setup -target_mounted" <BR> 5. Follow the rest of the instructions to install. <BR> 6. Type "vi /mnt/etc/fstab" and enter an appropriate fstab. <BR> As an example, here's what mine contains: <BR> <BR>/dev/hdb2 swap swap defaults <BR>/dev/hda2 / ext2 defaults <BR>/dev/hda3 /usr xiafs defaults <BR>/dev/hda1 /dos msdos defaults <BR>/dev/hdb1 /os2 msdos defaults <BR>none /proc proc defaults <BR> <BR> To give you some more info about this file, the first field is the <BR> partition to be mounted, the second is where it should be mounted, the <BR> third is the filesystem type, and the last field is the options to use. <BR> Unless you're a Linux wizard, just set this to "defaults". <BR> <BR> Other things to remember about this file: <BR> - Make sure that you list the root partition before any other partitions <BR> that are mounted beneath it. <BR> - Add the /proc line, or "ps", "w", etc, won't work. <BR> - It's a good idea to put a blank line at the end of the file, as I've <BR> had reports that partitions listed on the last line might not be <BR> mounted. <BR> <BR> 7. Once you've made and saved this file you can reboot with ctrl-alt-delete. <BR> <BR>----- <BR> <BR>Q: I have a (PS/1 || Valuepoint || Thinkpad), and can't install because fdisk <BR> can't see my hard drive. How can I get around this? <BR> <BR>A: You'll need to enter your drive parameters at the bootkernel prompt. You <BR> can even specify the geometry for your second IDE drive by supplying a <BR> second hd= parameter right after the first one. <BR> <BR> When you boot the bootkernel disk, you'll see more information about the <BR> format used to pass your drive parameters to the kernel at the LILO prompt <BR> and allow your drive to be recognized. <BR> <BR> You'll have to edit your lilo.conf file to add a similar hd= flag if you <BR> want LILO to work. Add this as the TOP line in the file: <BR> <BR> append="hd=cyl,hds,secs" <BR> <BR> Where "cyl", "hds", and "secs" are the number of cylinders, sectors, <BR> and heads on the drive. <BR> <BR> If you have two IDE drives, specify both drives (like this): <BR> <BR> append="hd=967,13,31 hd=944,14,40" <BR> <BR>----- <BR> <BR>Q: Why do my /etc/issue and /etc/motd keep resetting themselves at boot time? <BR> <BR>A: The /etc/rc.d/rc.S resets them out every time you boot after figuring out <BR> which kernel you're running -- otherwise the kernel version printed at login <BR> might not stay current. <BR> <BR> If you want to write your own /etc/issue and /etc/motd, you need to comment <BR> out that part of /etc/rc.d/rc.S. <BR> <BR>----- <BR> <BR>Q: Emacs dumps core, complains of a missing library, or lacks X11 support! Why? <BR> <BR>A: The GNU Emacs series includes your choice of a version with X11 support, or <BR> one without. Make sure you have the right binary for your machine. <BR> <BR> The binary supporting X11 is installed as part of a package on the first <BR> disk that you'll need to install whether you want X11 support or not. If <BR> you DO NOT want X11 support, install the package 'emac_nox.tgz' on the last <BR> disk of the Emacs series. <BR> <BR> If you just install all of the disks, you don't get X11 support. It had to <BR> be one way or the other, so if you're not paying attention when you install <BR> at least this way it will run no matter what. <BR> <BR>----- <BR> <BR>Q: Why do my compiles sometimes die with 'signal 11: internal compiler error'? <BR> <BR>A: This indicates a hardware problem in about 99% of the cases. It can usually <BR> be fixed by increasing the number of wait states in the CMOS settings. It <BR> can almost always be fixed by turning off the RAM cache, but this should be <BR> your last resort since it will cause a noticeable slowdown. <BR> <BR>----- <BR> <BR>Q: How can I change (or get rid of) the color ls? <BR> <BR>A: Read the man page, and check out the file /etc/DIR_COLORS. You can <BR> configure the colors any way you like, or shut them off entirely. Also, you <BR> can copy /etc/DIR_COLORS into your home directory as '.dir_colors' to <BR> override the global defaults on a user by user basis. <BR> <BR>----- <BR> <BR>Q: I start X with "openwin" and it works OK, but I can't switch virtual <BR> consoles. Why? <BR> <BR>A: On a Linux text screen, you switch virtual consoles with Alt-F1 through <BR> Alt-F8. Under XFree-86, you must use Ctrl-Alt-F1 through Ctrl-Alt-F8. <BR> Another useful 'secret' key combination is RightShift-PgUp/PgDown for <BR> scrollback. (a random amount ranging from none to a few pages, depending <BR> on the state of your video text buffer memory) <BR> <BR>----- <BR> <BR>Q: Why can't I use the new ghostscript with X? <BR> <BR>A: Make sure you have gs_x11.tgz from disk XAP1 installed. <BR> <BR>----- <BR> <BR>Q: I can't get anything to work at all! What's the deal? <BR> <BR>A: If you seem to suffer catastrophic failure (!), then check the file FILE_LIST <BR> on ftp.cdrom.com in /pub/linux/slackware against the contents of your disks <BR> and make sure you're not missing any files. <BR> <BR> Also, I've noticed that most of the reports of kernel panics and system <BR> hangs have come from people with 4MB. If you're running into these types <BR> of problems I'd suggest forking over the $$$ for 4 more meg. I have 8 MB of <BR> RAM and never have crashes. (well, only when I really push my luck) <BR> If you don't want to do that, then go through your /etc/rc.d/rc.* files and <BR> get rid of any daemons you don't use, like crond, lpd, or selection. <BR> <BR> If you've got 4 MB and you're getting 'virtual memory exceeded in new' <BR> warnings, make sure you set up and activate a swap partition before running <BR> setup. If you're really hard up on memory, you can boot a rootdisk using <BR> 'editroot' instead of one of the usual boot kernels. This will mount the <BR> floppy in the root drive, and you'll have to install from the other drive <BR> or from the hard drive. You will also not be able to create any kind of boot <BR> disk, so you'll have to install LILO and take your chances. I only suggest <BR> using this approach if a swapfile will not work. <BR> <BR>----- <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -