Tags:
create new tag
, view all tags
See BLT.

I decided to "mirror" version 2.2 final of the Filesystem Hierarchy Standard on WikiLearn. (This is something of a limited mirror as I do not anticipate updating to the next version unless I find (or make) a very simple to use automatic tool to recreate the TWiki markup for the next version.)

See FHS and Linux Filesystem Hierarchy Standard Discussion).

I made the decision to mirror it after the following "discussion" (with myself).

As I continue to add definitions for the various subdirectories, I am starting to quote from the FHS for almost every subdirectory. Yet, I'm not quoting everything. Two points:
  • I may be doing others a disservice by quoting portions of the FHS instead of trying to insist that they go back and read the actual document itself.
  • I need to recheck (for the third time) the license on the FHS. I initially started quoting thinking this was fair use (and it may still be), and, IIRC, the license does allow publishing modified versions (which this might be) but may require that the license or copyright notice (or something) be published along with it. I may have to do something more than I'm doing. I'll continue with the directory definitions and then decide what to do.
  • Or, maybe I should "publish" the FHS in its entirety (in accordance with their rules) on WikiLearn in "TWiki-ized" format. See /boot for the beginnings of an example of that (or at least the page I was doing when I thought of this approach).

OK, the more I think about that approach, the more I like it. I'd probably try to divide it across quite a few WikiLearn pages and then link it together in the expected way (by the chapters and headings in the standard), but then also link to it with links like /boot (made up example, probably wrong section number). Am I doing double work?? Doesn't something that serve the same purpose exist elsewhere on the Internet? Am I adding anything to it? Should I try to do other standards the same way?

After further thought I decided to make it all one big read only page -- the reason to have smaller pages is either to improve navigation during reading or make editing in the HTML TEXTAREA easier. I made the headings in the document into HTML headers and provided two TWiki tables of content which I believe addresses the problem of navigation during reading. The problem of editing in the TEXTAREA is mute in this case because the page is (and should be) read only. (I did my editing in Word and then copied and pasted it to WikiLearn.)

I don't know -- this might be an experiment to see if it does add something, followed by some exploration of other stuff. So far, I haven't found the FHS online in "online readable form" (I downloaded it as text) -- if it's not somewhere in online readable form it should be, and it should have a logical link structure. (Then I could potentially link to it from WikiLearn (assuming I avoid any violation of "deep linking" rules or norms).)

If other standards are worth doing the same way, I should think about creating (or finding) a DocBook to TWiki converter (or SGML, or whatever the source file format of the standards is). Ahh, the source is groff (if that's the way to express it) -- and it doesn't appear to exist in online readable format, at least on the FHS home site (http://www.pathname.com/fhs/).

Contributors

  • RandyKramer - 24 Jan 2002
  • <If you edit this page, add your name here, move this to the next line>
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2002-01-29 - RandyKramer
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding WikiLearn? WebBottomBar">Send feedback
See TWiki's New Look