[CALUG] CALUG Meeting Ideas

[Jim Sansing]

>From Brandon's original post, it sounds like he is
suggesting that we take the main commands for
admin'ing various components and describe the
arguments and result fields for them.  This will
require some background info, but not detailed
internals.  Sort of an interactive HOWTO.

>From some of the follow-ups, it seems like some
folks want to move into more advanced topics,
such as security and development.  I expect that
within this group, we can cover all of the basics
and a lot of advanced topics

I created a web page based on Brandon's list and
ftp'ed it to calug.org (Bernie, when you get a
chance please post it, including a link on the meetings
page, and let Chuck know--thanks.)  I suggest that
anyone who will take a topic or wants to add to the
list, send Chuck Fullerton an email.

The main thing to remember about making a
presentation is that it is about sharing information.
I did a presentation on subversion after working
with it for about 6 months.  There were several
questions I couldn't answer, but other people at
the meeting pitched in.  So you don't have to be
an uber-geek and you can be sure that CALUG
members appreciate your effort.

Later . . .   Jim

Chuck Fullerton wrote:
>Chris, et al.
>
>My TCP/IP Fundamentals presentation is from a Hacker's point of view but not
>very vendor specific.  If someone were to follow up with a presentation on
>how to set up TCP/IP and networking on different distro's and the
>differences between them, and maybe some other stuff, I'm thinking it might
>be pretty good.
>
>i.e.  I know Red Hat's Distros but if you ask me to set up FreeBSD or Debian
>with Networking, I'd have to do some research first.
>
>Whaddya think?
>
>Chuck. 
>
>-----Original Message-----
>From: Worsley, Christopher [mailto:Christopher.Worsley at hp.com] 
>Sent: Monday, May 14, 2007 9:39 PM
>To: Chuck Fullerton; Danyelle Gragsone; calug at unknownlamer.org
>Subject: RE: [CALUG] CALUG Meeting Ideas
>
>
>When you say linux networking do you mean administrative activities like
>controlling interfaces (ifconfig/iwconfig), more programming (i.e., writing
>client/server apps using tcp or udp), or networking drivers (such as the
>prism2/madwifi/acx100)?
>
>Cheers,
>
>Christopher
>
>
>-----Original Message-----
>From: calug-bounces at unknownlamer.org
>[mailto:calug-bounces at unknownlamer.org] On Behalf Of Chuck Fullerton
>Sent: Monday, May 14, 2007 4:54 PM
>To: 'Danyelle Gragsone'; calug at unknownlamer.org
>Subject: Re: [CALUG] CALUG Meeting Ideas
>
>I'd be willing to do a TCP/IP Fundamentals presentation... If someone would
>be willing to follow it up with a Linux Networking piece.
>
>Chuck. 
>
>-----Original Message-----
>From: calug-bounces at unknownlamer.org
>[mailto:calug-bounces at unknownlamer.org]
>On Behalf Of Danyelle Gragsone
>Sent: Monday, May 14, 2007 4:44 PM
>To: calug at unknownlamer.org
>Subject: Re: [CALUG] CALUG Meeting Ideas
>
>Greetings,
>
>I wouldn't mind a File systems and networking talk.
>
>
>Danyelle
>
>On 5/14/07, Brandon Checketts <brandon at brandonchecketts.com> wrote:
>  
>>Anybody interested in a meeting that takes an in-depth look at some 
>>aspect of
>>    
>>Linux internals.   Any particular topic may not warrant a full 2 hours
>>    
>on it's
>  
>>own, but maybe have two or three people each talk for 30-45 minutes on
>>    
>one?
>  
>>Sample ideas:
>>  - File systems: In-depth look at ext3 + info about others (ReiserFS,
>>    
>GFS, etc)
>  
>>  - Startup process in-depth (boot loader -> kernel load -> init scripts)
>>    
>>  - Memory management (interpreting 'free', 'vmstat', VSZ, RSS etc)
>>  - Process management (interpeting load average, Signaling, nice, etc)
>>    
>>  - Networking (netstat, iptables, etc)
>>
>>
>>I don't know if we have any experts on any of these topics, but most 
>>of us, as users, have probably researched into one or more of these 
>>areas a little bit on our own.  Giving a presentation on one would 
>>allow you to perhaps dig in a little deeper on a topic than you may
>>    
>otherwise get to.
>  
>>
>>Thanks,
>>Brandon Checketts
>>
>>