Parent Directory | Revision Log
|Links to HEAD:||(view) (download) (as text) (annotate)|
all the way up to mkswap still working on https://alioth.debian.org/tracker/index.php?func=detail&aid=301161&group_id=30283&atid=410673
add in ID tag thing for cvs updates
working on version 98
Reworked my notes inside the first dashed box in _Appendix VIII, Verify that system will boot even with one disk off-line_
Changed Ferdy Nagy (Nagy Fagy?) to Ferdy N. because I don't think that was his real name anyway and it looks bad on the document to flaunt this type of discrimitatory tag. If he doesn't want to use his real name so be it, but a rude tag like that on the document disrespects our readers and our efforts. Ferdy N. is perhaps a reasnonable compromise.
Added a couple lines in Appendix VIII to talk about mdadm --fail and mdadm --remove.
version .97 Add in support for grub directions,per patch. Fixed spelling errors started working on cleaning up grammar and spelling errors.
Fixed spelling errors. Added disaster recovery information. Updated initrd information. Added info on determing ide devices on system. Fixed some organizational/spacing errors.
working on next .95 version. adding in directions for using mkinitrad and initrd to use with stock kernel Need to put all initrd/mkinitrd in same section as it is currently in two spots. Added section for disaster recovery but have not put any information in it. Working on it.
Spellchecked document with 'ispell'. I am a bad speller and had spelled synchronize as cynchronize in several places. Fixed that. Also, changed 'cp -anx ...' to 'cp -aux ...' in a few places. There is no '-n' switch in 'cp' and it refuses to run with it. I believe the '-u' switch was intended.
on creation of mdadm.conf file it needs to have DEVICE instead of DEVICES. mdadm.conf file is important for mdadm to work correctly!
fixed more spelling errors, need to run it through spell check again.
fixed stupid stuff, republishing, and commented out swap items while I research it.
Updated installer links for woody and sarge to correct link. Roger, I think adding in troubleshooting information is a great idea!
- Consolidated two separate Appendix entries about "copying files" under one Appendix heading. - Added an Appendix entry, "VIII. Verify that system will boot even with one disk off-line."
*** empty log message ***
added resolution of my DMA problem in note in Step 6.4 -- I did not have my PCI chipset support compiled into my kernel. Recompiling with the correct PCI chipset support for my computer fixed my DMA off problem :-). I do not know if these kinds of notes in the document are worth keeping. But as long as they do not compromise readability, perhaps they are worth keeping. They might help others.
Added a new Appendix entry, 'IX. Setting up a RAID 1 Swap device.'
Added dashed line to the "note" style defenition at top (the note is at Step 6.4). Don't know if I like this extra farmatting idea for notes. Maybe only for some notes or untill the note gets blunded into the procure better. Won't know till I try this style out a bit. This is a document under construction, with various parts in various stages draft shages. So it may be helpful to use some formatting conventions to indicate like this when something is a "note" that has perhaps not been edited fully into the procedure itself, and thus stands appart from it. The "todo" formatting is another example of this, and is yellow currently but in any case different from "note" formatting. The written word is a graphical event. I believe if used correctly, this kind of sematic formating aid is very helpful. It can be difficult to use it well. Restaint is key. Do it only when it is semantically helpful, like saying "this is the page title," or "this is a level one header," or "this is a paragraph," etc.
added a 'note' class to the style defenitions at top, and used a <div class="note"> tag to set appart my note in Step 6.4 so that it does not interfier with readability of the procedure.
added notes at Step 6.4
fixed a typo (added a space after <boot-parameter-here>).
removed a blank <p class="todo">, an artifact from a resolved "todo" item.
added some notes (in section 2.2 and Appendix X.) including some "Roger is not sure about this" type notes, class="todo", that appear highlighted in yellow. I think it is better to put these notes directly into the document, rather than in bug reports, so that anyone reading the document will know there is a bug there. This is not a program run by computers. It is a document read by humans. So the filing of bug reports seems poor management of complexity to me when the notes can be more easily included in the document itself. I could be mistaken about that. I am just following what seems right editing procedure to me, in terms of editing documents. I don't mind learning as I go along thought :-).
spell checked entire document with ispell -- corrected some misspellings.
added a note to 6.1 and corrected "-add" in 6.2 to "--add".
added '-t' switch in 'mkfs -t reiserfs /dev/md0' command in section 3.4
I suspect, from what happened, that local copy is automatically merged with newly checked out copy when there is a local copy with same filename in local pwd at checkout time. This seems quite important to note. And I will adopt practice of appending '.old' to my local copy before checkout, to avoid this problem.
Testing that I understand how checkout and commit work. Specifically, I am trying to find out if I need to delete my local copy of rootraiddoc.html before I check out the CVS copy. It is not clear to me yet.
1) Earlier I had erroneously made all occurances of 'raid' in doc uppercase. But commands typically need it lowercase as it was before. So I changed it back to lowercase in commands. 2) Corrected some other commands that I had managed to munge previously when working on doc.
updated internal version to external version.
fixed cfdisk refer to device added in full lilo.conf file added in performance optimization sections.
"Roger Chrisman" <email@example.com> made these improvements - formatting, HTML and CSS. o added some CSS classes and defined them at top o added just a few in-line styles where classes didn't seem needed. - outline/headers o separated the Procedure into 6 steps o separated those 6 steps into sub-steps o added a Summary o moved all the other notes into an Appendix - content editing o edited the wording of explanations only for clarity o added some explanations o edited the 'code' . changed hdb to hdc . changed - to -- as in '--option' when option was spelled out . added a 'cat /etc/modules' step in Verify RAID Kernel step
*** empty log message ***
republishied to get it right.
Initial entyr internal version .86
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.
|Powered by ViewVC 1.1.5|