📄 00000040.htm
字号:
Your mileage may vary.) They're available at many places on the Web. <BR> They also ought to be on your file system in /usr/doc/HOWTO. Change to <BR> that directory, type ls | more, and see if any of the titles look like <BR> they'd help. If you find a likely looking prospect, you can view it in <BR> your favorite text editor (or use cat | more to view it on your <BR> console screen), and you can even print it if you've got your printer <BR> working. (Hint: If you can connect to the Web in some other operating <BR> system, you can find the HOWTO you want on the Web and print it from <BR> that other operating system.) <BR> <BR> Asking someone else <BR> <BR> Words of Wisdom #6: Buy yourself a good Linux book.Linux for Dummies <BR> will do wonders for getting started, and there are several good books <BR> for more advanced users. (Personal recommendation: Books published by <BR> O'Reilly are usually quite helpful, though they can be quite technical <BR> too. I also keep a copy of IDG's Red Hat Linux Secrets by my computer <BR> at all times.) <BR> Check the bookshelf here at *LNO* <BR> (URL: <A HREF="http://www.linuxnewbie.org/bookshelf/index.html">http://www.linuxnewbie.org/bookshelf/index.html</A> ) <BR> <BR> Words of Wisdom #7: <BR> If you bought a distribution that comes with tech support, give it a <BR> shot. Not all tech support is created equal, so this may or may not <BR> help. <BR> <BR> Words of Wisdom #8: <BR> Look around on the Web for answers. In particular, try linuxnewbie.org <BR> (see WoW #9 before you post), linux.com, linux.org, and the Web site <BR> associated with your distribution, if there is one. (Competing <BR> distributions may have helpful Web sites, too. I know Red Hat <BR> maintains some pretty good generic support files on their site.) <BR> <BR> Words of Wisdom #9: <BR> Ask in a newsgroup or bulletin board. I heartily recommend <BR> www.linuxnewbie.org (a.k.a. LNO) for this. You're more likely to get <BR> an answer than a lecture. But before you post your question... <BR> 1. Search for an answer. Somebody else may already have asked that <BR> same question. LNO's bulletin boards have a search link. <BR> Newsgroups can be searched at <A HREF="http://www.deja.com.">http://www.deja.com.</A> <BR> 2. Define your question as specifically as possible. Don't just say, <BR> "I can't get my sound card to work." Do say: <BR> a. I am trying to get (fill in the blank) to work. If it's a <BR> hardware question, mention brand, model number, <BR> PCI/ISA/AGP/USB, and in general enough information that I <BR> could walk into a store and be confident that I am walking <BR> out with the same thing you've got. For X-Windows questions, <BR> tell everything you know about your graphics card. If it's a <BR> software problem, say what version you're using. <BR> b. I am running Mandrake 6.0 (or whatever distribution you've <BR> got). <BR> c. I have tried x and y and z. That indicates that you have made <BR> a good-faith effort to fix the problem on your own (probably <BR> learning also makes it less likely that you'll get a bunch of <BR> responses telling you to try what you've already tried <BR> without success. <BR> d. If you're getting error messages, pass them on verbatim along <BR> with the command that caused them. <BR> e. If you are running on a Mac, Sparc, or anything other than an <BR> Intel-compatible, you need to say so. It might not matter, <BR> but then again it might save you from trying something that <BR> has no chance whatsoever of working. <BR> 3. You're asking people to help you out of the goodness of their <BR> hearts. So be polite, and make it as easy as possible for someone <BR> to understand the problem and help you out. In particular (my pet <BR> peeve), a post that has reasonably accurate grammar and spelling <BR> is a lot easier to follow. Even more important, use paragraphs to <BR> break up a screenful of text. (If you and paragraphs don't get <BR> along, try hitting the enter key twice after every third <BR> sentence.) <BR> <BR> Wanna add something to the WoW? <A HREF="mailto:sensei@linuxnewbie.org">sensei@linuxnewbie.org</A> <BR> ----------------------- <BR> Note added 1/03/2000 <BR> By: W. Cochran <BR> <BR> Keep a trouble log at hand. That's ink on paper. <BR> <BR> -When something goes wrong, write down the details. All of 'em. Right <BR> away. Don't wait even a minute: panic obliterates short-term memory. <BR> -Recording the problem forces you to be logical, gives you time for <BR> deep-breathing exercises, & makes the first draft for an SOS. <BR> <BR> -List everything that happened, & everything you try. <BR> -Use the news writer's 5 Ws & H: Who? What? Where? When? Why? How? <BR> -Oh, you've found a fix? Write that down, too -- no matter how easy or <BR> obvious it seems in your relief. Memory grows furtive. <BR> <BR> =======End============ <BR>-- <BR>|======================+========================+====================| <BR>| 以无法为有法 , | 拳本无法,有法也空; | 我爱GNU/Linux, | <BR>| 以无限为有限 | 一法不立,无法不容。| 因为我爱自由! | <BR>| | | | <BR>| 截拳道宗师-李小龙 | 意拳宗师-王芗斋 | 土人 Linuxrat | <BR>|======================+========================+====================| <BR> <BR>※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.112.168.253] <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -