I just got frustrated with the flame war on kernel building.
I'd like to at least try to put together something along the lines of documentation.
So far I've gone to the fabulous steps of:
export CVSROOT=:pserver:anonymous@rhlinux.redhat.com:/usr/local/CVS cvs -z3 login cvs -z3 co fedora-docs cd fedora-docs/ cp -r example-tutorial/ kernel-compilation-tutorial cd kernel-compilation-tutorial/ mv example-tutorial-en.xml kernel-compilation-tutorial-en.xml gvim ~/.vimrc gvim kernel-compilation-tutorial-en.xml gvim Makefile make
All this is useless except that the page is no longer blank.
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
Your work is welcome. A couple hints on how to proceed:
1. Check out the Quick Start Guide [1] for an easy to read intro to how things [are supposed to] work with FDP. Especially important is the section on what you as a writer should be doing other than just working through the ideas.
2. You might want to learn enough Emacs to make your DocBook XML editing easier. I never knew more vi than I needed to get by, but learning the same amount of Emacs wasn't any more difficult. The Docs Guide [2] has a chapter on using psgml, but there's also nXML and psgmlx out there too.
3. You should include a better Introduction in your tutorial. Doing this helps you get an idea of what you want to accomplish in the tutorial, and also what you *don't* want to accomplish. That helps keep you on point and prevents your document from spinning off-topic. If you want an example, I will humbly offer my mirror-tutorial as an example. My current build is viewable at http://docs.frields.org -- you will find other docs there that are not good examples, but the mirror-tutorial follows guidelines we hashed out on the list previously.
Thanks for participating!
[1] http://fedora.redhat.com/participate/documentation-quick-start/ [2] http://fedora.redhat.com/participate/documentation-guide/
On Tue, 2004-09-28 at 17:46 -0400, Paul W. Frields wrote:
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
Your work is welcome. A couple hints on how to proceed:
- Check out the Quick Start Guide [1] for an easy to read intro to how
things [are supposed to] work with FDP. Especially important is the section on what you as a writer should be doing other than just working through the ideas.
Ya I read it, sigh. I was going to just make a text file but nooOOoo I get to learn how to make it all pretty.
- You might want to learn enough Emacs to make your DocBook XML editing
easier. I never knew more vi than I needed to get by, but learning the same amount of Emacs wasn't any more difficult. The Docs Guide [2] has a chapter on using psgml, but there's also nXML and psgmlx out there too.
gvim seems to be doing an ok job. It likes REALLY big indents but whatever. I'll give emacs another go though.
- You should include a better Introduction in your tutorial. Doing this
helps you get an idea of what you want to accomplish in the tutorial, and also what you *don't* want to accomplish. That helps keep you on point and prevents your document from spinning off-topic.
I'll definitely want to flesh it out more for sure. I don't quite know enough to get too off topic. And the more people try to tell me to include stu
If you want an example, I will humbly offer my mirror-tutorial as an example. My current build is viewable at http://docs.frields.org -- you will find other docs there that are not good examples, but the mirror-tutorial follows guidelines we hashed out on the list previously.
Thanks for participating!
[1] http://fedora.redhat.com/participate/documentation-quick-start/ [2] http://fedora.redhat.com/participate/documentation-guide/ -- Paul W. Frields, RHCE
I'll check those out for sure.
On Tue, 2004-09-28 at 19:44, Kevin H. Hobbs wrote:
On Tue, 2004-09-28 at 17:46 -0400, Paul W. Frields wrote:
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
Your work is welcome. A couple hints on how to proceed:
- Check out the Quick Start Guide [1] for an easy to read intro to how
things [are supposed to] work with FDP. Especially important is the section on what you as a writer should be doing other than just working through the ideas.
Ya I read it, sigh. I was going to just make a text file but nooOOoo I get to learn how to make it all pretty.
- You might want to learn enough Emacs to make your DocBook XML editing
easier. I never knew more vi than I needed to get by, but learning the same amount of Emacs wasn't any more difficult. The Docs Guide [2] has a chapter on using psgml, but there's also nXML and psgmlx out there too.
gvim seems to be doing an ok job. It likes REALLY big indents but whatever. I'll give emacs another go though.
- You should include a better Introduction in your tutorial. Doing this
helps you get an idea of what you want to accomplish in the tutorial, and also what you *don't* want to accomplish. That helps keep you on point and prevents your document from spinning off-topic.
I'll definitely want to flesh it out more for sure. I don't quite know enough to get too off topic. And the more people try to tell me to include stu
If you want an example, I will humbly offer my mirror-tutorial as an example. My current build is viewable at http://docs.frields.org -- you will find other docs there that are not good examples, but the mirror-tutorial follows guidelines we hashed out on the list previously.
Thanks for participating!
[1] http://fedora.redhat.com/participate/documentation-quick-start/ [2] http://fedora.redhat.com/participate/documentation-guide/ -- Paul W. Frields, RHCE
I'll check those out for sure.
Kevin,
Thanks for writing this. It is a much needed tutorial. I moved the open bug to block the docs in progress tracker instead.
I co-authored an article in the first issue of Wide Open Magazine about the 2.6 kernel, including how to recompile it. I'll compare your version with mine and see if I can add to it. Please send me your latest version if you have made any changes since the version you posted and I can send you a patch. Or, if you prefer I can just list the changes in an email. Let me know which you prefer.
Cheers, Tammy
Tammy
On Thu, 2004-09-30 at 11:10 -0400, Tammy Fox wrote:
On Tue, 2004-09-28 at 19:44, Kevin H. Hobbs wrote:
On Tue, 2004-09-28 at 17:46 -0400, Paul W. Frields wrote:
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
Your work is welcome. A couple hints on how to proceed:
- Check out the Quick Start Guide [1] for an easy to read intro to how
things [are supposed to] work with FDP. Especially important is the section on what you as a writer should be doing other than just working through the ideas.
Ya I read it, sigh. I was going to just make a text file but nooOOoo I get to learn how to make it all pretty.
- You might want to learn enough Emacs to make your DocBook XML editing
easier. I never knew more vi than I needed to get by, but learning the same amount of Emacs wasn't any more difficult. The Docs Guide [2] has a chapter on using psgml, but there's also nXML and psgmlx out there too.
gvim seems to be doing an ok job. It likes REALLY big indents but whatever. I'll give emacs another go though.
- You should include a better Introduction in your tutorial. Doing this
helps you get an idea of what you want to accomplish in the tutorial, and also what you *don't* want to accomplish. That helps keep you on point and prevents your document from spinning off-topic.
I'll definitely want to flesh it out more for sure. I don't quite know enough to get too off topic. And the more people try to tell me to include stu
If you want an example, I will humbly offer my mirror-tutorial as an example. My current build is viewable at http://docs.frields.org -- you will find other docs there that are not good examples, but the mirror-tutorial follows guidelines we hashed out on the list previously.
Thanks for participating!
[1] http://fedora.redhat.com/participate/documentation-quick-start/ [2] http://fedora.redhat.com/participate/documentation-guide/ -- Paul W. Frields, RHCE
I'll check those out for sure.
Kevin,
Thanks for writing this. It is a much needed tutorial. I moved the open bug to block the docs in progress tracker instead.
I co-authored an article in the first issue of Wide Open Magazine about the 2.6 kernel, including how to recompile it. I'll compare your version with mine and see if I can add to it. Please send me your latest version if you have made any changes since the version you posted and I can send you a patch. Or, if you prefer I can just list the changes in an email. Let me know which you prefer.
Cheers, Tammy
Tammy
Sorry, I got behind on my e-mail. Paul Frields gave me some pointers, but I would appreciate any input available. I started this because all I could find was the flamewar.
On Wed, 2004-10-06 at 22:41, Kevin H. Hobbs wrote:
On Thu, 2004-09-30 at 11:10 -0400, Tammy Fox wrote:
On Tue, 2004-09-28 at 19:44, Kevin H. Hobbs wrote:
On Tue, 2004-09-28 at 17:46 -0400, Paul W. Frields wrote:
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
Your work is welcome. A couple hints on how to proceed:
- Check out the Quick Start Guide [1] for an easy to read intro to how
things [are supposed to] work with FDP. Especially important is the section on what you as a writer should be doing other than just working through the ideas.
Ya I read it, sigh. I was going to just make a text file but nooOOoo I get to learn how to make it all pretty.
- You might want to learn enough Emacs to make your DocBook XML editing
easier. I never knew more vi than I needed to get by, but learning the same amount of Emacs wasn't any more difficult. The Docs Guide [2] has a chapter on using psgml, but there's also nXML and psgmlx out there too.
gvim seems to be doing an ok job. It likes REALLY big indents but whatever. I'll give emacs another go though.
- You should include a better Introduction in your tutorial. Doing this
helps you get an idea of what you want to accomplish in the tutorial, and also what you *don't* want to accomplish. That helps keep you on point and prevents your document from spinning off-topic.
I'll definitely want to flesh it out more for sure. I don't quite know enough to get too off topic. And the more people try to tell me to include stu
If you want an example, I will humbly offer my mirror-tutorial as an example. My current build is viewable at http://docs.frields.org -- you will find other docs there that are not good examples, but the mirror-tutorial follows guidelines we hashed out on the list previously.
Thanks for participating!
[1] http://fedora.redhat.com/participate/documentation-quick-start/ [2] http://fedora.redhat.com/participate/documentation-guide/ -- Paul W. Frields, RHCE
I'll check those out for sure.
Kevin,
Thanks for writing this. It is a much needed tutorial. I moved the open bug to block the docs in progress tracker instead.
I co-authored an article in the first issue of Wide Open Magazine about the 2.6 kernel, including how to recompile it. I'll compare your version with mine and see if I can add to it. Please send me your latest version if you have made any changes since the version you posted and I can send you a patch. Or, if you prefer I can just list the changes in an email. Let me know which you prefer.
Cheers, Tammy
Tammy
Sorry, I got behind on my e-mail. Paul Frields gave me some pointers, but I would appreciate any input available. I started this because all I could find was the flamewar.
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
Have you created a bug for what you have done already?
Or, do you have it posted somewhere where it can be reviewed?
Sorry, I got behind on my e-mail. Paul Frields gave me some pointers, but I would appreciate any input available. I started this because all I could find was the flamewar.
Have you created a bug for what you have done already?
Or, do you have it posted somewhere where it can be reviewed?
I don't have the bug # handy, but try searching the open fedora-docs bugs on Bugzilla. There aren't that many of them, so it's not hard to find, I'm sure.
On Wed, 2004-10-06 at 13:21, tuxxer wrote:
[snip]
Have you created a bug for what you have done already?
Or, do you have it posted somewhere where it can be reviewed?
Yes, the bugzilla entry is: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130754
On Tue, 2004-09-28 at 14:19, Kevin H. Hobbs wrote:
I just hacked together what I understand form the flamewars. I am about to try to follow my own instructions now and see if I'm even close. :-)
Coments are absolutely welcome. I really have no idea what I'm doing.
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
I seem to have a half decent kernel compilation document done, at least as far as my needs are concerned. It works ( I'm running on my custom kernel) but I have no idea if it is the way one SHOULD build a custom kernel on Fedora.
The document is on bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130754
docs@lists.stg.fedoraproject.org