[SPARCbook] A Proposal (?) - revising the User Guide to Solaris 2.6 w/o NCE

Sat Jun 24 17:11:46 CDT 2000

This is a multi-part message in MIME format.

------=_NextPart_000_0078_01BFDE07.A855DD00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I was thinking today that traffic on this list has dropped down =
considerably
once we all (nearly all?) got a fairly recent solaris build on our boxes =
and
added HD/RAM as desired (within the limits of the hardware) - so what is
next to discuss?

I am wondering if there is interest in going through the User =
documentation
and "updating" it to reflect our exp. with the hardware, now that we are =
at
Solaris 2.6 (without NCE)? My thinking is that if folks were to each =
take a
small chunk of the users guide, say a chapter, and then go through and
mark it up with changes/make a list of changes in a short period of time
we could have "up to date" documentation (sort of). This update would be
viewed as a supplement to the existing FAQ and web sites, it would =
simply
translate references to man pages with re-worked examples from the users
guide to reflect Solaris 2.6.

I do not envision anyone re-typing the manual, but if updates were =
provided
a person could, say, put a few errata pages at the back of each chapter =
with
updated examples/discussions...

This is just a thought, but I thought this might be something folks =
would
want to have with their SPARCBooks.

Comments?

Ken

------=_NextPart_000_0078_01BFDE07.A855DD00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I was thinking today that traffic on =
this list has=20
dropped down considerably</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>once we all (nearly all?) got a fairly =
recent=20
solaris build on our boxes and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>added HD/RAM as desired (within the =
limits of the=20
hardware) - so what is</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next to discuss?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I am wondering if there is interest in =
going=20
through the User documentation</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and "updating" it to reflect our exp. =
with the=20
hardware, now that we are at</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Solaris 2.6 (without NCE)? My thinking =
is that if=20
folks were to each take a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>small chunk of the users guide, say a =
chapter, and=20
then go through and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>mark it up with changes/make a list of =
changes in a=20
short period of time</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we could have "up to date" =
documentation (sort of).=20
This update would be</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>viewed as a supplement to the existing =
FAQ and web=20
sites, it would simply</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>translate references to man pages with =
re-worked=20
examples from the users</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>guide to reflect Solaris =
2.6.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I do not envision anyone re-typing the =
manual, but=20
if updates were provided</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a person could, say, put a few errata =
pages at the=20
back of each chapter with</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>updated =
examples/discussions...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>This is just a thought, but I thought =
this might be=20
something folks would</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>want to have with their =
SPARCBooks.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Comments?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Ken</FONT></DIV></BODY></HTML>

------=_NextPart_000_0078_01BFDE07.A855DD00--