[RHCE] Raleigh study group

[Jim Ray]

that bbt location might be the best bet if space is available.  otherwise,
my wife confirmed again tonight that once a week is fine at my house one
block from the ncsu library on vanderbilt ave.  i have another room with a
20" monitor, kvm switch and lots of computers that are available for
tinkering.  shoot, i even have a domain name not really in use with dynamic
dns.  we could do some real live internet stuff and make accounts for
everyone in the class to do more tinkering. parking can be an issue over
here, though.  ncsu territory.

parking or no, we do have the advantage here in that no one else will be
using the facilities; so, we can set it up to our mutual liking and not have
to worry about anyone making changes between classes.  plenty of switched
ports and fast internet here.

we've got lots of folks to go on and at least try to find a common
denominator on the calendar.  i say once a week on any given evening mon,
tue, wed or thur and leave the weekend free for family stuff.  if once a
week is too much, every other week is fine, too.  i just assume do once a
week and get on with it.

let's hold an organizational meeting, bring calendars, decide on whatever
study materials we will use and get started.

> -----Original Message-----
> From: Kevin Flanagan [mailto:kevin at flanagannc.net]
> Sent: Thursday, August 28, 2003 6:11 PM
> To: jim at neuse.net; Red Hat Certified Engineer exam study group
> Cc: kflanagan at bbandt.com
> Subject: RE: [RHCE] Raleigh study group
>
>
> I'm fairly sure that I could host the group in Raleigh on
> Atlantic Ave,
> just between Old Wake Forest and Capital exits off of 440. We
> could use
> a conference room, I have network gear, and some systems, PII400
> Proliant servers.  The only thing is that a BB&T employee
> would have to
> be there at all times.  There is another person at work who is
> interested in the study group too.    If everyone had a laptop, or
> lugable desktop, we could easily have a couple of monitors, keyboards
> etc there.
>
>
>
> Kevin
>