I don't think that TLDP is like a technical manual, it's a great way to find out ANY stuff you want to know, I've been using TLDP as my knowledge base since i was 13. And I really must say that <a href="http://linuxforums.org">
linuxforums.org</a> do a great job at helping people, it's not geeky but it may seem a bit difficult at first. but when you try it, it will be all fine. Or you can always try the qunu project<br><br>cheers<br><br><div>
<span class="gmail_quote">On 6/29/07, <b class="gmail_sendername">Jacob Maynard</b> <<a href="mailto:indymaynard@maynard.homelinux.com">indymaynard@maynard.homelinux.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is exactly what I'm talking about. It's imperative that we get a<br>great design for putting this information out to people. We don't need<br>another forum. People set up forums all of the time, and they are great
<br>for geeks. Normal users get so confused looking at them, though. And they<br>don't want to take the time to register for an account.<br><br>I totally agree with you, greenarrow.<br><br>Jacob<br><br>> On 6/26/07, Matthew Flaschen <
<a href="mailto:matthew.flaschen@gatech.edu">matthew.flaschen@gatech.edu</a>> wrote:<br>>> Graham Cox wrote:<br>>> > There are distro-specific parts that are needed - how you install<br>>> software on
<br>>> > Ubuntu is very different to how you do so on Gentoo - but there is a<br>>> lot more<br>>> > that is not distro specific at all.<br>>> ><br>>><br>>> And there are collated tutorials on these general issues. For example,
<br>>> there's the Linux Documentation Project.<br>>><br>>> Matt Flaschen<br>>><br>>> _______________________________________________<br>>> Advocate mailing list<br>>> <a href="mailto:Advocate@badvista.org">
Advocate@badvista.org</a><br>>> <a href="http://badvista.fsf.org/mailman/listinfo/advocate">http://badvista.fsf.org/mailman/listinfo/advocate</a><br>>><br>><br>> Can you honestly say the Linux Documentation Project is written in the
<br>> way a Windows user just coming to Linux would understand? And, when<br>> searching for this how does the new Linux wannabe search for it? Its<br>> not even on the first couple of pages if you search Linux newbie.
<br>> Just like selling a new toy, without it listed in plain view so<br>> everyone could see it, plus good illustrations it is not going to<br>> sell.<br>><br>> We need a general site that is not written or designed like it is a
<br>> technical manual. Window users are not going to read if it is written<br>> like it is from a tech manual. We need some active content and get<br>> away from the straight geek type set ups. Linux programmers are even
<br>> beginning to see this. I seen a big change in the way OpenSUSE is<br>> being generated now. Easier to comprehend, you see screenshots, more<br>> active content in materials and getting away from the hohum military
<br>> style of writing instructions.<br>><br>> George<br>> greenarrow1<br>> InNetInvestigations-Forensic<br>> SuSe 10.2/TriStar/Apache<br>> GoBoLinux<br>><br>> _______________________________________________
<br>> Advocate mailing list<br>> <a href="mailto:Advocate@badvista.org">Advocate@badvista.org</a><br>> <a href="http://badvista.fsf.org/mailman/listinfo/advocate">http://badvista.fsf.org/mailman/listinfo/advocate
</a><br>><br><br><br><br>_______________________________________________<br>Advocate mailing list<br><a href="mailto:Advocate@badvista.org">Advocate@badvista.org</a><br><a href="http://badvista.fsf.org/mailman/listinfo/advocate">
http://badvista.fsf.org/mailman/listinfo/advocate</a><br></blockquote></div><br><br clear="all"><br>-- <br>\ \ / /__ _ __ (_) | |_ | |_ <br>.\ V// _` |(_-< | || _| | ' \<br> |_| \__,_|/__/ |_| \__||_||_|<br>
<a href="http://tuxv.blogspot.com">http://tuxv.blogspot.com</a><br>09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 <br>Don't send me word attachments.<br><a href="http://www.gnu.org/philosophy/no-word-attachments.html">
http://www.gnu.org/philosophy/no-word-attachments.html</a>