I think I will because I have downloaded the technical papers from SIS, and I have a good idea of how the card works So how do I go about writing a howto - ie is there a specific format?
Subject: Re: [ILUG-BOM] XF86Config Modelines From: Philip S Tellis philip.tellis@iname.com
Maybe you'd like to write this as a mini-Howto. I know that there are many people who've had similar problems with 6326. Also, 6215 is still unsupported in X4.1.0, so if anyone knows of any way to use it in 4, that would be good, or someone could look at writing the driver.
Philip
-- "Language shapes the way we think, and determines what we can think about." -- B. L. Whorf
Visit my webpage at http://www.ncst.ernet.in/~philip/ Read my writings at http://www.ncst.ernet.in/~philip/writings/
MSN philiptellis Yahoo! philiptellis AIM philiptellis ICQ 129711328
On Mon, Dec 24, 2001 at 06:49:37PM +0530, Vijay Joaquim Stevens wrote:
I think I will because I have downloaded the technical papers from SIS, and I have a good idea of how the card works So how do I go about writing a howto - ie is there a specific format?
Subject: Re: [ILUG-BOM] XF86Config Modelines From: Philip S Tellis philip.tellis@iname.com
Maybe you'd like to write this as a mini-Howto. I know that there are many people who've had similar problems with 6326. Also, 6215 is still unsupported in X4.1.0, so if anyone knows of any way to use it in 4, that would be good, or someone could look at writing the driver.
If you are serious and would like to learn something that will stay with you for a life time: follow this URL: http://db.ilug-bom.org.in/Documentation/LDP-Author-Guide/
Nagarjuna
--- Vijay Joaquim Stevens gwendolyn@now-india.net.in wrote:
I think I will because I have downloaded the technical papers from SIS, and I have a good idea of how the card works So how do I go about writing a howto - ie is there a specific format?
http://www.linuxdoc.org/LDP/LDP-Author-Guide/index.html
"There are many ways to contribute to the Linux movement without actually writing code. One of the most important is writing documentation, allowing each person to share their knowledge with thousands of others around the world. This Guide is designed to help you get familiar with how the LDP works, and what tools you'll need to write your own HOWTO."
Basically it talks about SGML and how to go about creating documents that will fit right in with the LDP ... pretty easy if you are familiar with Emacs. Will be glad to help with it ... I have been using Docbook SGML and Emacs in sgml mode for writing the Newbie's Guide.
SameerDS.
===== -- MTech Student Reconfigurable Computing Lab KReSIT, IIT-Bombay
__________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com
----- Original Message ----- From: Vijay Joaquim Stevens gwendolyn@now-india.net.in Subject: Re: [ILUG-BOM] XF86Config Modelines
I think I will because I have downloaded the technical papers from
SIS,
and I have a good idea of how the card works So how do I go about writing a howto - ie is there a specific
format?
well...i believe there is a HOWTO-HOWTO!!! ;-) umm..if u want to make it official, http://www.linuxdoc.org/HOWTO/HOWTO-INDEX/writing.html should help
regards, kishor
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Sometime on Dec 24, Vijay Joaquim Stevens assembled some asciibets to say:
So how do I go about writing a howto - ie is there a specific format?
I think others have replied with relevant links, you could read them, but I generally find it easier to write the howto first, and then make it conform to standards.
This is my nano-Howto-Howto:
Title by Author v x.y.z, date
Three line summary
1. About this document
1.1 Copyright ...
1.2 Discalaimer ...
1.3 Feedback/contacting the author ...
1.4 Where to get the latest version ...
2. Introduction Describe the problem here
3. Solution Describe possible solutions, as well as your solution here
4. Further configuration specific configuration that may be required in special cases, or based on special user requirements
5. Acknowledgements
6. References
7. Further reading