1
0
mirror of https://github.com/fspc/gbootroot.git synced 2025-03-04 03:43:23 -05:00

Shows the check boxes for NSS and PAM.

This commit is contained in:
freesource 2001-12-07 06:17:00 +00:00
parent 5aeb0b8c63
commit 83b2b22388

View File

@ -3,7 +3,7 @@
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E"
alink="#FF0000">
<center>$Id: index.html,v 1.39 2001/12/06 23:14:40 freesource Exp $</center>
<center>$Id: index.html,v 1.40 2001/12/07 02:40:59 freesource Exp $</center>
<p>
@ -309,6 +309,15 @@ templates (ex: Examples) or template links to be saved
with their own name; after you make changes to these kind of templates,
save them with a new name to preserve the changes.</p>
<p><IMG ALT="" SRC="images/settings.jpg" align="center"></p>
<p>
Edit->Setttings has two check boxes which allow you to turn on and off
the automatic NSS and PAM configuration files parsing behavior described
in detail in Example.yard and Example-Mini.yard.
<p><IMG ALT="" SRC="images/stripping.jpg" align="center"></p>
<p>
@ -584,7 +593,7 @@ users to send me all their problems.&nbsp;&nbsp;Why?&nbsp;&nbsp;I love bugs,
and I have experience working in Quality Assurance, so I know that a
program like gbootroot is loaded with glitches unforeseen
by the developer.&nbsp;&nbsp;I consider
anything a bug which effects the user negatively,
a bug anything which effects the user negatively,
whether it is a user interface (UI) which is hard to understand
or use, documentation which seems misleading, or if the program doesn't
seem to deliver results as it should.&nbsp;&nbsp;Even if you think