BEGIN{ open F,"Makefile"; our $top_dir=pop @{[split /\s/,(grep /^top_srcdir/,<F>)[0]]}; eval "use lib '$top_dir'"; close F; }
use My::Web;
-require "CGI";
-use project::captive::doc::Macros;
+require CGI;
+BEGIN { Wuse 'project::captive::doc::Macros'; }
-My::Web->init(
+project::captive::doc::Macros->init(
"__PACKAGE__"=>__PACKAGE__,
"title"=>'Captive NTFS Developer Documentation: Captive vs. Linux-NTFS',
- "head_css"=>$doc_Macros_head_css,
+ "rel_prev"=>'Related.html.pl',
);
-My::Web->heading();
print <<"HERE";
<p><span class="re">> It would have to run as part of the kernel which would mean
that if it went wrong it could crash the machine. With no source, we might not
be able to work around the problem.</span><br />
- @{[ a_href '#sandbox','Nope' ]},
+ @{[ a_href 'Details.html.pl#sandbox','Nope' ]},
@{[ a_href 'http://lufs.sourceforge.net/lufs/','Linux Userland File System (LUFS)' ]}
moves the filesystem implementation to UNIX userland where the Microsoft
Windows filesystem is completely unarmed by Captive jail of chroot(2),
the other kernel coders would not investigate any problems if someone had used
the NTFS wrapper.</span><br />
It does not apply to this project due to the implemented
- @{[ a_href '#sandbox','filesystem separation' ]}.</p>
+ @{[ a_href 'Details.html.pl#sandbox','filesystem separation' ]}.</p>
HERE
-My::Web->footer();
+project::captive::doc::Macros->footer();