The organizers of the local "Kernel-panic Linux User Group" (KPLUG)
thanked Bryen and myself after our presentations after a well-received
and very active evening and noting that the meeting attendance far
exceeded their normal turnout.

Because we considered that everyone in attendance were already users
of some version of Linux, we modified our presentation content to
focus on how openSUSE could help their choice of Distro and then later
describe openSUSE not found in others instead of a rote listing of
Distro features.

Bryen opened with an overview of how the openSUSE umbrella now
encompasses much more than just the Distro. I (Tony) followed up
expanding on various openSUSE technologies, then took a short break to
switch from the location's "presentation" laptop to a laptop running
openSUSE for "live" demos.

I (Tony) had determined that what most distinguished openSUSE from
other distros was YAST, so almost all of the remainder of the evening
was based on stepping through the YAST applets, which of course in
turn also provided the framework for touching on just about all
aspects of openSUSE in general (eg When talking about YAST software
management, we also touched on the Zypper and RPM tools, and repeated
earlier descriptions of OBS).

Throughout the evening, we repeatedly mentioned openSUSE'
interoperability, excellent hardware support, extensive list of
software packages, and in particular ease of both hardware and
software configuration.

Both during and after the presentations Bryen and I fielded a number
of questions related to the Microsoft/Novell arrangement, the
philosophy and direction of openSUSE and of course basic questions
like "How do I get openSUSE?" and "Which download do I really want?"
and "I'm running XP, what do I have to do to install openSUSE?"

A Thanks to Izabel Valverde and Carlos Alberto visiting from Brazil
for their contributions during the evening as well.

Hope all other launch parties were this successful!

Tony
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to