[NTLUG:Discuss] linux newbie manual

Thu Mar 7 19:11:59 CST 2002

Brian and everyone,
I will license this under free license.  I want to post this on ntlug's
site, and also on www.linuxnewbie.org, if I get their permission.  Can we
license it before it's finished?  If so, I'll do that right now.  I do
understand the awkwardness of hosting it on a coorporate training site, so
if i get permission, i would really like to put in on ntlug's site as soon
as possible.  But if noone really cares, then we'll just leave it on PD's
site.
Because this will be a free license documentation, i'm always looking for
other places where we may submit this material for internet and non-internet
postings.
When, and not if, I start publishing this in book form, I want to donate the
profits to ntlug and their operations.  I have no need for profits gained
from publishing this, as I will be using it myself to teach Linux classes.
This project started out as a hobby, as I was tutoring some friends from
Rockwall, TX in Linux administration to pass the now-bankrupt (and possible
illegitimate) company called linuxgruven.  I was going to be giving them the
manual to help improve their teaching materials, which were very hard to
understand.  But since their business practices were ethically questionable,
and I am affiliated with another company, I have no desire to do so.
I updated the website to address all these concerns:
http://www.prodirections.com/linux
----- Original Message -----
From: <brian at pongonova.net>
To: <discuss at ntlug.org>
Sent: Thursday, March 07, 2002 12:57 PM
Subject: Re: [NTLUG:Discuss] linux newbie manual


> Micky--
>
> Do you have plans on releasing this document under a free license?  Or
> will distribution be restricted by some sort of proprietary license?
> Reason I ask is that I would be glad to help proofread it if the
> document wasn't encumbered with any type of license/copyright
> restrictions.  Othewise, if I'm going to help you proofread a document
> that will retain commercial restrictions on distribution, derivation,
> etc., I'd expect to be compensated accordingly.
>
> The only reason I bring this up is I noticed the site you're hosting
> the document on is a corporate training site.
>
>   --Brian
>
> On Thu, Mar 07, 2002 at 05:14:12PM -0600, micky hotmail wrote:
> > yes, definately doing security later.
> > ...on a new note, would it better not to post this project on this
> > newsgroup?  If someone pointed me in the right direction (or if someone
> > wanted to do it for me, which would be great, since i'm low on time for
the
> > next month), we could create a list just for this newbie documentation
> > project.
> > I need to contact www.linuxnewbie.org to see if they would want to help
> > contribute to this project (and vice-versa).
> > -Micky
> > ----- Original Message -----
> > From: <kbrannen at gte.net>
> > To: <discuss at ntlug.org>
> > Sent: Wednesday, March 06, 2002 11:01 PM
> > Subject: Re: [NTLUG:Discuss] linux newbie manual
> >
> >
> > > Cameron Moore wrote:
> > >
> > > ...
> > > >
> > > > The next logical question is: So what do I use?  Well, that depends.
If
> > > > you need a word processor, you could look into using OpenOffice[2].
I
> > > > personally don't like OpenOffice because it's relatively bloated if
all
> > > > you want to do is view documents.  Based on my own personal
experience
> > > > creating documentation for an open-source project[3], I would use
LaTeX.
> > > > From LaTex sources, you can generate a PDF, PostScript, HTML, or
some
> > > > other file format.  It is really quite powerful, but you forfeit
> > > > ease-of-use for flexibility (comparied to a WYSIWYG editor).  I
haven't
> > > > used it, but there is a WYSISYG editor for LaTeX called Lyx[4].
Might
> > > > want to give it a go.
> > > ...
> > > > [4] http://www.lyx.org/
> > > >
> > >
> > >
> > > I'll definitely second (and third!) Lyx as an publishing tool.  I've
used
> > it
> > > to create a 15 page document before, then "publish" it in several
formats,
> > > including HTML.
> > >
> > > A quick overview of the networking page shows:
> > >
> > > ---quote---
> > > [inetd secion] Any time you change any networking configuration file,
you
> > must
> > > restart the daemon.  The inetd daemon is restarted by issuing the
command
> > > /etc/rc.d/init.d/inetd restart. ...
> > > ---quote---
> > >
> > > True, however you might also want to point out that you can cause the
> > daemon
> > > to reread it's configuration file (inetd.conf) by sending the inetd
> > process a
> > > HUP signal.  [Side note since you said you were going to cover xinetd
in
> > the
> > > future; to force xinetd to reread its config file, you must send it
the
> > USR1
> > > signal.  It took me a while find that out...grrrr...]
> > >
> > > In the ftp section, you might want to point out there are multiple ftp
> > > packages available, with an overview of pros/cons of each.  Or
warnings to
> > > stay away from certain packages if at all possible. :-)
> > >
> > > There is a lot of good stuff in there, good job!  I can tell you
aren't
> > done
> > > yet, but formatting will be a major job...good luck!
> > >
> > > I don't see anything about security.  An oversight or is that in the
part
> > > that's not written yet?  Security is a major part of networking.  I'm
> > talking
> > > about stuff like:  turning off services you don't need, not installing
> > some
> > > packages, checking logs, not allowing "easy" passwords, etc.  I saw
the
> > > section on firewalls, but I guess I'm talking about overall security.
> > >
> > > I'll try to read more later.  Good job and good luck!
> > >
> > > Kevin
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > http://www.ntlug.org/mailman/listinfo/discuss
> > >
> >
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>