LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2003-09-27 17:20:48 +00:00
parent 894a98697e
commit b87feaddd4
2 changed files with 1411 additions and 1394 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
LDP/howto/docbook/XFree-Local-multi-user-HOWTO.xml
View File

@ -1,7 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" []>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "file://localhost/usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd">
<book id="index">
<bookinfo>
<!-- Use "HOWTO", "mini HOWTO", "FAQ" in title, if appropriate -->
@ -17,6 +15,12 @@
<pubdate>Sep 2003</pubdate>
<!-- Most recent revision goes at the top; list in descending order -->
<revhistory>
<revision>
<revnumber>1.2.1</revnumber>
<date>2003-09-25</date>
<authorinitials>SS</authorinitials>
<revremark>yet another bugfix release :( - fix BusID (x:xx.x vs x:xx:x) again</revremark>
</revision>
<revision>
<revnumber>1.2</revnumber>
<date>2003-09-17</date>
@ -756,19 +760,19 @@ EndSection
<caution>
<para>For the older(version 1) Preferred Bus ID XFree Server only this choice is valid.</para>
</caution>
<para>For example on command line <screen format="linespecific">[root@svetljo mnt]# startx -- /usr/X11R6/bin/X0 :0 -prefbusid 1:0.0 vt7</screen> , or from a display manager (gdm): <programlisting format="linespecific">..............................
<para>For example on command line <screen format="linespecific">[root@svetljo mnt]# startx -- /usr/X11R6/bin/X0 :0 -prefbusid 1:0:0 vt7</screen> , or from a display manager (gdm): <programlisting format="linespecific">..............................
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X0 :0 -layout first-Xserver -deferglyphs 16 -ac -prefbusid 1:0.0 vt7
command=/usr/X11R6/bin/X0 :0 -layout first-Xserver -deferglyphs 16 -ac -prefbusid 1:0:0 vt7
flexible=true
[server-Second]
name=Second server
command=/usr/X11R6/bin/X1 :1 -layout second-Xserver -deferglyphs 16 -prefbusid 0:13.0 vt9
command=/usr/X11R6/bin/X1 :1 -layout second-Xserver -deferglyphs 16 -prefbusid 0:13:0 vt9
flexible=true
.............................. </programlisting> and for xdm/kdm <programlisting format="linespecific">:0 local /bin/nice -n -10 /usr/X11R6/bin/X0 :0 -deferglyphs 16 -prefbusid 1:0.0 vt7
:1 local /bin/nice -n -10 /usr/X11R6/bin/X1 :1 -xf86config /etc/X11/XF86Config-4.TNT2 -prefbusid 0:13.0 vt9</programlisting></para>
.............................. </programlisting> and for xdm/kdm <programlisting format="linespecific">:0 local /bin/nice -n -10 /usr/X11R6/bin/X0 :0 -deferglyphs 16 -prefbusid 1:0:0 vt7
:1 local /bin/nice -n -10 /usr/X11R6/bin/X1 :1 -xf86config /etc/X11/XF86Config-4.TNT2 -prefbusid 0:13:0 vt9</programlisting></para>
</listitem>
</itemizedlist>
</listitem>
@ -805,25 +809,7 @@ ln -s XFree[modified] X2
</listitem>
</itemizedlist>
<note>
<itemizedlist>
<listitem>
<para>For the older(version 1) Preferred Bus ID XFree Server you also have to specify the desired graphic card with parameter <quote><command>-prefbusid x:x:x</command></quote>, where x:x:x is the Bus ID of the desired graphic card.</para>
<itemizedlist>
<listitem>
<para>For AGP cards, something similar to <command>-prefbusid 1:0:0</command></para>
</listitem>
<listitem>
<para>For PCI cards, something similar to <command>-prefbusid 0:x:0</command> (x is normally the IRQ number)</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>In the following explanation I will not use this option. If you use the Preferred Bus ID X server just append <command>-prefbusid x:x:x</command> with the correct Bus ID of the card you want to start right before the last argument <command>vt[x]</command> .</para>
</listitem>
<listitem>
<para>In case you are using the latest(version 2) prefbusid patch/ binary you may omit the <command moreinfo="none">-prefbusid x:x:x</command> argument when starting X, but you have to specify the correct settings in the XFree configuration file(s).</para>
</listitem>
</itemizedlist>
<para>Have in mind that for the older Preferred Bus ID XFree Server (version 1) you have to specify the desired graphic card with parameter <quote><command>-prefbusid x:x:x</command></quote> where x:x:x is the Bus ID of the desired graphic card. Just append "-prefbusid x:x:x" with the correct Bus ID of the card you want to start right before the last argument vt[x].</para>
</note>
<para>If you have 3 video cards, 3 keyboards, and you have started the Backstreet Ruby kernel with dumbcon=2, you can start 3 independent X servers for 3 simultaneous users with the following commands:</para>
<para></para>
@ -2391,7 +2377,7 @@ your display manager will start a single X server with the corresponding XF86Con
</sect1>
<sect1 id="dyn_switch_num_x_serv">
<title>Dynamically switching the number of X servers</title>
<para>There is a very experimental GUI/CLI for dynamically switching the number of running X servers. It uses the automatic configuration of the display managers (mentioned in <xref linkend="automation_multy_snd-cards"/>), Python, dialog for the CLI, and Xdialog for the GUI.</para>
<para>There is a very experimental GUI/CLI for dynamically switching the number of running X servers. It uses the automatic configuration of the display managers (mentioned in <xref linkend="auto_dm_confs"/>), Python, dialog for the CLI, and Xdialog for the GUI.</para>
<para>Once it is more tested and bug-free, you could, for example, use it under Backstreet Ruby to switch between 2, 3 or more X servers and a single X server using Xinerama. So when your PC isn't used by more then one user, you could use the other monitors under Xinerama. Or one more funny example: you're simulating net gaming with a number of friends on your bruby Linux PC, you have invested a bit more in an additional graphic card which is already configured, but you don't have enough money right now to buy one more monitor and keyboard/mouse pair. One friend of yours comes and says, <quote>Hey guys, that's cool. Can I join?</quote> What would you answer? Using the GUI could result in the following answer from your side: <quote>No problem, just bring your monitor,keyboard and mouse.</quote></para>
<para>If you are feeling like a hacker and want to try out this BUGGY GUI/CLI, check the current status at <ulink url="http://varna.demon.co.uk/~svetlio/ruby-contrib/bruby-python/">http://varna.demon.co.uk/~svetlio/ruby-contrib/bruby-python/</ulink>. But remember, it's not very tested, and if not configured properly it can cause you serious troubles. Please wait until it is more stable if you are not that familiar with Linux. If you feel comfortable enough under Linux, and think of yourself as a hacker, please help in testing it and making it better, bug-free and easy to configure.
</para>

399
LDP/howto/linuxdoc/User-Group-HOWTO.sgml
View File

@ -4,7 +4,7 @@
<title>Linux User Group HOWTO
<author><url name="Rick Moen" url="mailto:rick@linuxmafia.com"></author>
<date>v1.6.7, 2003-08-04
<date>v1.6.8, 2003-09-27
<abstract>
The Linux User Group HOWTO is a guide to founding, maintaining, and
@ -22,7 +22,7 @@ The Linux User Group HOWTO is intended to serve as a guide to founding,
maintaining, and growing a Linux user group.
Linux is a freely-distributable implementation of Unix for personal
computers, servers, and workstations. It was developed on the i386 and
computers, servers, workstations, PDAs, and embedded systems. It was developed on the i386 and
now supports i486, Pentium, Pentium Pro, Pentium II, Pentium III, and
Pentium IV processors, as well as IA32 clones from AMD, Cyrix, VIA, IDT,
Winchip, NexGen, Transmeta, VIA C3 Ezra "CentaurHauls", and others. It
@ -74,8 +74,8 @@ please: <bf>Free programmers are happy programmers are effective
programmers</bf>.
However, this loose structure can disorient the new Linux user: Whom
does she call for support, training, or education? How does she know for
what uses Linux is suitable?
does she call for support, training, or education? How does she know
what Linux is suitable for?
In large part, LUGs provide the answers, which is why LUGs are
vital to the Linux movement: Because your town, village, or metropolis
@ -92,7 +92,7 @@ they are done by a LUG.
<sect1>What is a user group?
<p>
Computer user groups, at least in the USA, are not new. In
Computer user groups are not new. In
fact, they were central to the personal computer's history:
Microcomputers arose in large part to satisfy demand for affordable,
personal access to computing resources from electronics, ham radio, and
@ -108,24 +108,22 @@ American user groups in their heyday produced newsletters, maintained
shareware and diskette libraries, held meetings and social events, and,
sometimes, even ran electronic bulletin board systems (BBSes). With the
advent of the Internet, however, many services that user groups once
provided migrated to things like CompuServe, AOL, and the Web.
provided migrated to things like CompuServe and the Web.
Linux's rise, however, coincided with and was intensified by the
general public "discovering" the Internet. As the Internet grew more
popular, so did Linux: The Internet brought to Linux new users,
developers, and vendors.
developers, and vendors. So, the same force that sent traditional user
groups into decline propelled Linux forward and inspired new groups
concerned exclusively with it.
So, just as traditional PC user groups were declining because of the
Internet's popularity, this popularity propelled Linux forward, creating
demand for new groups concerned exclusively with Linux. To give just one
indication of how LUGs differ from traditional user groups, I point out
a curious fact: Traditional user groups must maintain fairly tight
control over what software its users may copy and trade at meetings.
To give just one indication of how LUGs differ from traditional
user groups: Traditional groups must closely
monitor what software users redistribute at meetings.
While illegal copying of restricted proprietary software certainly
occurred, it was officially discouraged -- and for good reason.
occurred, it was officially discouraged -- for good reason.
At LUG meetings, however, that entire mindset simply does not apply:
Far from being what a LUG must discourage, unrestricted copying of Linux
Far from being forbidden, unrestricted copying of Linux
should be among a LUG's primary goals. In fact, there is anecdotal
evidence of traditional user groups having difficulty adapting to
Linux's ability to be lawfully copied at will.
@ -136,20 +134,19 @@ Check licence terms, if in doubt.)
<sect1>Summary
<p>
For the Linux movement to continue to flourish, along with other
factors, LUGs must proliferate and succeed. Because of Linux's
unique status, LUGs must provide some of the same functions a "regional
For the Linux movement to grow, among other requirements,
LUGs must proliferate and succeed. Because of Linux's
unusual nature, LUGs must provide some of the same functions a "regional
office" provides for large computer corporations like IBM, Microsoft,
and Sun. LUGs can and must train, support, and educate Linux users,
coordinate Linux consultants, advocate Linux as a computing solution,
and even serve as liaison to local media outlets such as newspapers and
television.
and even serve as liaison to local news outlets.
<sect>What LUGs exist?
<p>
Since this document is meant as a guide not only to maintaining and
growing LUGs but also to founding them, we should, before going further,
discuss what LUGs exist.
discuss what LUGs already exist.
<sect1>LUG lists
<p>
@ -264,7 +261,7 @@ their advocacy is effective, well-supported, and free.
<sect1>The limits of advocacy
<p>
Advocacy can be misaimed; advocacy can go wrong and be
Advocacy can be mis-aimed; advocacy can go wrong and be
counterproductive; advocacy can be simply inappropriate in the first
place. The matter merits careful thought, to avoid wasted time or
worse.
@ -283,30 +280,30 @@ receptive.
Along those lines, bear in mind that, for many people, perhaps most, an
"advocate" is perceived as a salesman, and thus classified as someone to
resist rather than listen to fairly. They've never heard of someone
being enthusiastic for getting them to adopt a piece of software without
standing to gain materially, so they assume there must be something in
it for you, and will overtly or unconsciously decide to argue back, and
suggest they'd be doing you a personal favour to even listen, let alone
urging them to adopt a piece of software without
benefiting materially, so they assume there must be something in
it for you and will push back, and
act as if they're doing you a personal favour to even listen, let alone
try your recommendations.
I recommend bringing such discussions back to a rational basis
I recommend bringing such discussions back to Earth
immediately, by pointing out that software policy should be based in
one's own long-term self interest, that you have no personal stake in
what choices they make, and that you certainly wouldn't want to force
them to listen to your analyses against their will. After that, if
one's own long-term self interest, that you have zero personal stake in
their choices, and that you have better uses for your time than speaking
to an unreceptive audience. After that, if
they're still interested, at least you won't face the same artificial
obstacle.
At the same time, make sure you don't live up to the stereotype of the
OS advocate, either. Just shoving your views at someone is downright
rude and offensive. Moreover, when done concerning Linux, it's
also clueless: Unlike the case with proprietary OSes, Linux will not
also pointless: Unlike the case with proprietary OSes, Linux will not
live or die by the level of corporate acceptance and release/maintenance
of ported applications. It and all key applications are open source:
the programmer community that maintains it is self-supporting, and would
keep it advancing and and healthy regardless of whether the business
world and general public uses it with wild abandon, only a little, or
not at all. Because of its open-source licence terms, its raw source
not at all. Because of its open-source licence terms, source
code is permanently available. Linux cannot be "withdrawn from the
market" at the whim of some company. Accordingly, there is simply no
point in pesky OS advocacy -- unlike that of some communities we could
@ -370,7 +367,7 @@ community and social organisations, and other non-corporate
environments. This accomplishes the goal of Linux advocacy and also
educates the general public. As more such organisations seek Internet
presence, provide their personnel dial-in access, or other
Linux-relevant funcitons, LUGs gain opportunities for community
Linux-relevant functions, LUGs gain opportunities for community
participation, through awareness and education efforts -- extending to
the community the same generous spirit characteristic of Linux and the
free software / open source community from its very beginning. Most
@ -415,10 +412,10 @@ will have it, too.
<sect1>Linux support
<p>
Of course, for the desperate <bf>newcomer</bf>, the primary role of a
Of course, for the <bf>newcomer</bf>, the primary role of a
LUG is Linux support -- but it is a mistake to suppose that Linux
support means only <it>technical</it> support for new Linux users. It
can and should mean much more.
should mean much more.
LUGs have the opportunity to support:
@ -431,43 +428,37 @@ LUGs have the opportunity to support:
<sect2>Users
<p>
New Linux users' most frequent complaint, once they have gotten Linux
installed, is the steep learning curve that is not unique to Linux but
is, rather, characteristic of all modern Unixes. With that learning
curve, however, comes the power and flexibility of a real operating
system. A LUG is often the a new user's only resource to flatten out the
learning curve.
New Linux users' most frequent complaint, once they have Linux
installed, is the steep learning curve characteristic of all modern
Unixes. With that learning curve, however, comes the power and
flexibility of a real operating system. A LUG is often the a new
user's main resource to flatten the learning curve.
However, even if a new Linux user doesn't yet know it, she needs more
than just support: Linux and the free software worlds are both moving
targets. LUGs form a valuable source of information on Linux and
other free software products. Not only does Linux lack a central
bureaucracy, but also for the most part lacks journalistic
infrastructure from which other computer systems' users benefit. The
movement does have resources like <url name="Linux Journal"
During Linux's first decade, it gained some first-class journalistic
resources, which should not be neglected: The main monthly magazines
of longest standing are <url name="Linux Journal"
url="http://www.linuxjournal.com/"> and <url name="Linux Gazette"
url="http://www.linuxgazette.com/">, but new users may be unaware of
them. In addition, being <it>monthly</it> publications, they're often out
of date about bug fixes, security problems, patches, new kernels, etc.
This is where LUGs as sources and conduits of timely information can be
vital to all Linux users.
url="http://www.linuxgazette.com/"> (on-line). More recently, they've
been joined by <url name="Linux Format" url="http://www.linuxformat.co.uk/">,
<url name="LinuxUser and Developer" url="http://www.linuxuser.co.uk/">,
and <url name="Linux Magazine" url="http://linux-magazine.com/">.
(Fairness requires amending the above old HOWTO text to mention standout
on-line news sources with weekly or better publication cycles, such as <url
name="Linux Weekly News" url="http://lwn.net/">, <url name="Linux
Today" url="http://linuxtoday.com">, <url name="FreshNews"
url="http://freshnews.org/">, and <url name="Newsforge"
url="http://newsforge.com/">.)
Standout on-line magazines with weekly or better publication cycles
include <url name="Linux Weekly News" url="http://lwn.net/">,
<url name="Linux Today" url="http://linuxtoday.com">,
<url name="FreshNews" url="http://freshnews.org/">, and
<url name="Newsforge" url="http://newsforge.com/">.
For example, until new Linux users know that the newest kernels are
available from <url name="ftp.kernel.org" url="ftp://ftp.kernel.org">
or that the <bf>Linux Documentation Project</bf> usually has newer
versions of Linux HOWTOs than does a CD-based Linux distribution,
LUGs, as primary support entities, should convey such
timely and useful information.
All of these resources have eased LUGs' job of spreading essential
news and information -- about bug fixes, security problems, patches,
new kernels, etc., but new users must still be made aware of
them, and taught that the newest kernels are always
available from <url name="ftp.kernel.org" url="ftp://ftp.kernel.org">,
that the <bf>Linux Documentation Project</bf> has newer
versions of Linux HOWTOs than do CD-based Linux distributions,
and so on.
In fact, it may be a bit misleading to focus on the support role
LUGs provide new users: intermediate and advanced users
Intermediate and advanced users
also benefit from proliferation of timely and useful tips, facts,
and secrets. Because of the Linux world's manifold aspects, even
advanced users often learn new tricks or techniques simply by
@ -477,31 +468,15 @@ they didn't know existed; sometimes, they just remember arcane
<sect2>Consultants
<p>
It is, I think, obvious to claim that LUGs should support new users.
After all, if they don't do that, what else is there? It may not be as
obvious that LUGs can be an important resource for Linux consultants.
Both full-time and otherwise, Linux consultants can be an important part
of a LUG. How can the LUG support them?
The answer is that of a related question: What do Linux consultants
need? <bf><it>They need someone for whom to consult.</it></bf> A LUG
provides the best way for those <it>offering</it> Linux consulting to
find those who <it>need</it> their services. The LUG can informally
broker connections between consulting suppliers and consulting
consumers, simply by getting people interested in Linux in contact, as
will be detailed. The vital point is that LUGs can and should fill
<it>this</it> role, as well. Although the Linux Consultants Guide is an
important resource, it surely lists only a small fraction of available
Linux talent.
The relationship is mutually beneficial: Consultants aid LUGs by
providing experienced leadership, both technically and organisationally,
while LUGs aid consultants by putting them in contact with potential
clients. New and inexperienced users gain benefit from both LUGs and
LUGs can help Linux consultants find their customers and vice-versa,
by providing a forum where they can come together.
Consultants also aid LUGs by providing experienced leadership.
New and inexperienced users gain benefit from both LUGs and
consultants, since their routine or simple requests for support are
handled by LUGs <it>gratis</it>, and their complex needs and problems --
the kind obviously requiring a paid consultant's services -- can be
handled by consultants the LUG helps them contact.
handled by LUGs <it>gratis</it>, while their complex needs and problems --
the kind requiring paid services -- can be fielded by consultants found
through the LUG.
The line between support requests needing a consultant and those
that don't is sometimes indistinct; but, in most cases, the difference
@ -544,11 +519,31 @@ politely suggest that her needs would be better served by paid
the borderline is inherently debatable and a likely source of
controversy.
Telltale signs that a questioner may need to be transitioned to consulting-based assistance include:
<itemize>
<item>An insistence on getting solutions in "recipe" (rote) form, with the apparent aim
of not needing to learn technological fundamentals.
<item>Asking the same questions (or ones closely related) repeatedly.
<item>Vague problem descriptions, or ones that change with time.
<item>Interrupting answers in order to ask additional questions (suggesting
lack of attention to the answers).
<item>Demands that answers be recast or delivered more quickly (suggesting
that the questioner's time and trouble but that helpers' are not).
<item>Asking unusually complex, time-consuming, and/or multipart questions.
</itemize>
In general, LUG members are especially delighted to help, on a volunteer basis, members
who seem likely to participate in the Linux "gift culture" by picking up its body of lore
and, in turn, perpetuate it by teaching others in their turn. Certainly, there's nothing
wrong with having other priorities and values, but such folk may in some cases be best
referred to paid assistance, as a better fit for both their needs.
An additional observation that may or may not be useful, at this point:
There are things one may be willing to do for free, to assist others in the
Linux community, that one will refuse to do for money: Shifting from
assisting someone as a volunteer fundamentally changes the relationship.
A fellow hobbyist who suddenly becomes a customer is a very different
A fellow computerist who suddenly becomes a customer is a very different
person; one's responsibilities are quite different, and greater. You're
advised to be aware, if not wary, of this distinction.
@ -560,7 +555,8 @@ international list of Linux consultants.
<p>
LUGs also have the opportunity to support local businesses and
organisations. This support has two aspects: First, LUGs can support
businesses and organisations wanting to use Linux as a part of their
businesses and organisations wanting to use Linux (and Linux-based
applications) as a part of their
computing and IT efforts. Second, LUGs can support local businesses
and organisations developing software for Linux, cater to Linux users,
support or install Linux, etc.
@ -570,12 +566,9 @@ a part of their computing operations differs little from the help LUGs
give individuals trying Linux at home. For example, compiling the Linux
kernel doesn't really differ. Supporting businesses, however, may
require supporting proprietary Linux software -- e.g., the Oracle, Sybase,
and DB2 databases (or VMware, Win4Lin, and such things). If Linux is to
maintain momentum as a viable, general computing environment, it needs
software vendors willing to write for (and port to) Linux as a
proprietary-application platform. If LUGs helps business users evaluate
proprietary Linux solutions, more software vendors will consider Linux
in their development and planning.
and DB2 databases (or VMware, Win4Lin, and such things).
Some LUG expertise in these areas may help businesses make the leap
into Linux deployments.
This leads us directly to the second kind of support a LUG can give to
local businesses: LUGs can serve as a clearinghouse for information
@ -602,7 +595,7 @@ organising charitable giving. <url name="Chris Browne"
url="mailto:cbbrowne@cbbrowne.com"> has thought about this issue as much as
anyone I know, and he contributes the following:
<sect3>Chris Browne on free software philanthropy
<sect3>Chris Browne on free software / open source philanthropy
<p>
A further involvement can be to encourage sponsorship of various
Linux-related organisations in a financial way. With the <url
@ -712,11 +705,11 @@ Education Foundation">
The Open Source Education Foundation's purpose to enhance K-12 education
through the use of technologies and concepts derived from The Open
Source and Free Software movement. In conjunction with Tux4Kids, OSEF
created a bootable distribution of GNU/Linux based on Klaus Knopper's
Knoppix, aimed at kids, parents, teachers, and other school officials.
OSEF installs and supports school computer labs, and has developed a
"K12 Box" as a compact Plug and Play workstation computer for student
computer labs.
created a bootable distribution of GNU/Linux (Knoppix for Kids) based
on Klaus Knopper's Knoppix, aimed at kids, parents, teachers, and
other school officials. OSEF installs and supports school computer labs,
and has developed a "K12 Box" as a compact Plug and Play workstation
computer for student computer labs.
<item> <url url="http://www.osafoundation.org/donations.htm" name="Open
Source Applications Foundation">
@ -740,7 +733,8 @@ organised. It isn't a corporation, but is important to businesses
everywhere. The best way for a LUG to support the international Linux
movement is to keep the local Linux community robust, vibrant, and
growing. Linux is <it>developed</it> internationally, which is easy
enough to see by reading <file>/usr/src/linux/MAINTAINERS</file> -- but
enough to see by reading the kernel source code's
<file>MAINTAINERS</file> file -- but
Linux is also <it>used</it> internationally. This ever-expanding
user base is key to Linux's continued success, and is where the LUGs
are vital.
@ -781,8 +775,8 @@ It is important that new Linux users come to learn what Linux culture,
concepts, traditions, and vocabulary. Linux acculturation, unlike "real
world" acculturation, can occur on mailing lists and Usenet, although
the latter's efficacy is challenged by poorly acculturated users and by
spam. LUGs are often much more efficient at this task than mailing lists
or newsgroups, precisely because of the former's greater interactivity
spam. LUGs are often much more efficient at this task than are mailing
lists or newsgroups, precisely because of the former's greater interactivity
and personal focus.
<sect>LUG activities
@ -832,7 +826,7 @@ pages, if not whole Web sites. In fact, I'm not sure how else to find a
LUG, but to check the Web.
It makes sense, then, for a LUG to make use of whatever Internet
technologies they can: Web sites, mailing lists, wikis, FTP, e-mail, Web
technologies they can: Web sites, mailing lists, wikis, ftp, e-mail, Web
discussion forums, netnews, etc. As the world of commerce is
discovering, the 'Net is an effective way to advertise, inform, educate,
and even sell. The other reason LUGs make extensive use of Internet
@ -872,7 +866,7 @@ spends considerable time discussing Web issues. Quoting it (in outline form):
<item>You may want to consider establishing a LUG mailing list.
<item>You don't need to be in the Internet Service Provider business.
<item>Don't go into any other business, either.
<item>Walk the walk.
<item>Walk the walk. (Do the LUG's computing on Linux.)
</itemize>
That essay partly supplements (and partly overlaps) this HOWTO.
@ -964,16 +958,16 @@ There are several organisations offering assistance to LUGs.
<itemize>
<item>Determine the nearest existing LUG</item>
<item>Announce your intentions on <tt>comp.os.linux.announce</tt> and on an appropriate regional hierarchy</item>
<item>Determine the nearest existing LUG.</item>
<item>Announce your intentions on <tt>comp.os.linux.announce</tt> and on an appropriate regional hierarchy.</item>
<item>Announce your intention wherever computer users are in your area: bookstores, swap meets, cybercafes, colleges and universities, corporations, Internet service providers, etc.</item>
<item>Find Linux-friendly businesses or institutions in your area willing to help you form the LUG</item>
<item>Form a mailing list or some means of communication among the people who express an interest in forming a LUG</item>
<item>Ask key people specifically for help in spreading the word about your intention to form a LUG</item>
<item>Solicit space on a Web server to put a few HTML pages together about the group</item>
<item>Begin looking for a meeting place</item>
<item>Schedule an initial meeting</item>
<item>Discuss at the initial meeting the goals for the LUG</item>
<item>Find Linux-friendly businesses or institutions in your area willing to help you form the LUG.</item>
<item>Form a mailing list or some means of communication among the people who express an interest in forming a LUG.</item>
<item>Ask key people specifically for help in spreading the word about your intention to form a LUG.</item>
<item>Solicit space on a Web server to put a few HTML pages together about the group.</item>
<item>Begin looking for a meeting place.</item>
<item>Schedule an initial meeting.</item>
<item>Discuss at the initial meeting the goals for the LUG.</item>
</itemize>
@ -982,39 +976,39 @@ There are several organisations offering assistance to LUGs.
<itemize>
<item>Make the barriers to LUG membership as low as possible</item>
<item>Make the LUG's Web site a priority: keep all information current, make it easy to find details about meetings (who, what, and where), and make contact information and feedback mechanisms prominent</item>
<item>Install Linux for anyone who wants it</item>
<item>Post flyers, messages, or handbills wherever computer users are in your area</item>
<item>Secure dedicated leadership</item>
<item>Follow Linus's <it>benevolent dictator</it> model of leadership</item>
<item>Take the big decisions to the members for a vote</item>
<item>Start a mailing list devoted to technical support and ask the "gurus" to participate on it</item>
<item>Schedule a mixture of advanced and basic, formal and informal, presentations</item>
<item>Support the software development efforts of your members</item>
<item>Find way to raise money without dues: for instance, selling Linux merchandise to your members and to others</item>
<item>Consider securing formal legal standing for the group, such as incorporation or tax-exempt status</item>
<item>Find out if your meeting place is restricting growth of the LUG</item>
<item>Meet in conjunction with swap meets, computer shows, or other community events where computer users -- i.e., potential Linux converts -- are likely to gather</item>
<item>Elect formal leadership for the LUG as soon as is practical: Some helpful officers might include President, Treasurer, Secretary, Meeting Host (general announcements, speaker introductions, opening and closing remarks, etc.), Publicity Coordinator (handles Usenet and e-mail postings, local publicity), and Program Coordinator (organises and schedules speakers at LUG meetings)</item>
<item>Provide ways for members and others to give feedback about the direction, goals, and strategies of the LUG</item>
<item>Support Linux and free software development efforts by donating Web space, a mailing list, or FTP site</item>
<item>Establish an FTP/Web site for relevant software</item>
<item>Archive everything the LUG does for the Web site</item>
<item>Solicit "door prizes" from Linux vendors, VARs, etc. to give away at meetings</item>
<item>Give credit where due</item>
<item>Join SSC's GLUE (Groups of Linux Users Everywhere) but be aware they charge a membership fee</item>
<item>Submit your LUG's information to all the LUG lists</item>
<item>Publicise your meetings on appropriate Usenet groups and in local computer publications and newspapers</item>
<item>Make the barriers to LUG membership as low as possible.</item>
<item>Make the LUG's Web site a priority: Keep all information current, make it easy to find details about meetings (who, what, and where), and make contact information and feedback mechanisms prominent.</item>
<item>Install Linux for anyone who wants it.</item>
<item>Post flyers, messages, or handbills wherever computer users are in your area.</item>
<item>Secure dedicated leadership.</item>
<item>Follow Linus's <it>benevolent dictator</it> model of leadership.</item>
<item>Take the big decisions to the members for a vote.</item>
<item>Start a mailing list devoted to technical support and ask the "gurus" to participate on it.</item>
<item>Schedule a mixture of advanced and basic, formal and informal, presentations.</item>
<item>Support the software development efforts of your members.</item>
<item>Find way to raise money without dues: for instance, selling Linux merchandise to your members and to others.</item>
<item>Consider securing formal legal standing for the group, such as incorporation or tax-exempt status.</item>
<item>Find out if your meeting place is restricting growth of the LUG.</item>
<item>Meet in conjunction with swap meets, computer shows, or other community events where computer users -- i.e., potential Linux converts -- are likely to gather.</item>
<item>Elect formal leadership for the LUG as soon as is practical: Some helpful officers might include President, Treasurer, Secretary, Meeting Host (general announcements, speaker introductions, opening and closing remarks, etc.), Publicity Coordinator (handles Usenet and e-mail postings, local publicity), and Program Coordinator (organises and schedules speakers at LUG meetings).</item>
<item>Provide ways for members and others to give feedback about the direction, goals, and strategies of the LUG.</item>
<item>Support Linux and free software / open source development efforts by donating Web space, a mailing list, or FTP site.</item>
<item>Establish an FTP/Web site for relevant software.</item>
<item>Archive everything the LUG does for the Web site.</item>
<item>Solicit "door prizes" from Linux vendors, VARs, etc. to give away at meetings.</item>
<item>Give credit where due.</item>
<item>Join SSC's GLUE (Groups of Linux Users Everywhere), but be aware they charge a membership fee.</item>
<item>Submit your LUG's information to all the LUG lists.</item>
<item>Publicise your meetings on appropriate Usenet groups and in local computer publications and newspapers.</item>
<item>Compose promotional materials, like Postscript files, for instance, members can use to help publicise the LUG at workplaces, bookstores, computer stores, etc.</item>
<item>Make sure you know what LUG members want the LUG to do</item>
<item>Make sure you know what LUG members want the LUG to do.</item>
<item>Release press releases to local media outlets about any unusual LUG events like an Installation Fest, Net Day, etc.</item>
<item>Use LUG resources and members to help local non-profit organisations and schools with their Information Technology needs</item>
<item>Advocate the use of Linux zealously but responsibly</item>
<item>Play to LUG members's strengths</item>
<item>Use LUG resources and members to help local non-profit organisations and schools with their Information Technology needs.</item>
<item>Advocate the use of Linux zealously but responsibly.</item>
<item>Play to LUG members' strengths.</item>
<item>Maintain good relations with Linux vendors, VARs, developers, etc.</item>
<item>Identify and contact Linux consultants in your area
<item>Network with the leaders of other LUGs in your area, state, region, or country to share experiences, tricks, and resources</item>
<item>Identify and contact Linux consultants in your area.</item>
<item>Network with the leaders of other LUGs in your area, state, region, or country to share experiences, tricks, and resources.</item>
<item>Keep LUG members advised on the state of Linux software -- new kernels, bugs, fixes, patches, security advisories -- and the state of the Linux world at large -- new ports, trademark and licensing issues, where Linus is living and working, etc.</item>
<item>Notify the Linux Documentation Project -- and other pertinent sources of Linux information -- about the documentation the LUG produces: technical presentations, tutorials, local HOWTOs, etc.</item>
</itemize>
@ -1031,7 +1025,7 @@ liability and helps the group carry insurance. It aids fundraising.
It avoids claims for tax on group income.
<it>Con:</it> Liability shouldn't be a problem for modestly careful
people. You're not doing skydiving, after all. Fundraising isn't needed
people. (You're not doing skydiving, after all.) Fundraising isn't needed
for a group whose activities needn't involve significant expenses.
(Dead-tree newsletters are so 1980.) Not needing a treasury, you avoid
needing to argue over it, file reports about it, or fear it being taxed
@ -1039,7 +1033,7 @@ away. Meeting space can usually be gotten for free at ISPs, colleges,
pizza parlours, brewpubs, coffeehouses, computer-training firms,
Linux-oriented companies, or other friendly institutions, and can
therefore be free of charge to the public. No revenues and no expenses
means less need for organisation and comcomitant hassles.
means less need for organisation and concomitant hassles.
For what it's worth, this HOWTO's originator and second maintainer lean,
respectively, towards the pro and con sides of the debate -- but choose
@ -1062,7 +1056,7 @@ attain:
</enum>
Although relevant statutes differ among states, most states
allow user groups to incorporate as non-profit entitites. Benefits
allow user groups to incorporate as non-profit entities. Benefits
of incorporation for a LUG include limitations of liability
of LUG members and volunteers, as well as limitation or even exemption
from state corporate franchise taxes.
@ -1121,16 +1115,16 @@ name="http://www.wegweiser-buergergesellschaft.de/praxishilfen/arbeit_im_verein/
following to say about the kinds of intra-LUG political dynamics that
often crop up (lightly edited and expanded by the HOWTO maintainer):
<sect2>People have different feelings about free software.
<sect2>People have different feelings about free / open-source software
<p>
Linux users are a diverse bunch. As soon as you try to put a lot of
them together, <it>some</it> problem issues can arise. Some, who are
nearly political radicals, believe all software, always, should be
"free". Because Caldera charges quite a lot of money for their
distribution, and doesn't give all profits over to <it>(pick favorite
advocacy organisation)</it>, they must be "evil". Ditto Red Hat or
advocacy organisation)</it>, it must be "evil". Ditto Red Hat or
SuSE. Keep in mind that all three of these companies have made and
continue to make significant contributions to free software.
continue to make significant contributions to free / open-source software.
(HOWTO maintainer's note: The above was a 1998 note, from before
Caldera exited the Linux business, renamed itself to The SCO Group,
@ -1174,7 +1168,7 @@ possible and encouraged.
proprietary-software vendors, e.g., in the Linux kernel, XFree86, and
gcc.
<item> Proprietary imples neither better nor horrible.
<item> Proprietary implies neither better nor horrible.
</itemize>
@ -1193,9 +1187,9 @@ skins.
<sect2>Non-profit organisations and money don't mix terribly well.
<p>
It is important to be careful with finances in any sort of non-profit.
In businesses, which focus on substative profit, people are not
In businesses, which focus on substantive profit, people are not
typically too worried about minor details such as alleged misspending of
immaterial sums. The same cannot be said about non-profit
immaterial sums. The same cannot be said of non-profit
organisations. Some people are involved for reasons of principle, and
devote inordinate attention to otherwise minor issues. LUG business
meetings' potential for wide participation correspondingly expands the
@ -1208,11 +1202,11 @@ can reasonably demand accountability. Fees not collected can't be
misused -- or squabbled over.
<p>
If there <it>is</it> a lot of money and/or other substantive property
If there <it>is</it> a lot of money and/or other substantive property,
the user group must be accountable to members.
<p>
Any vital, growing group, should have more than one active person. In
Any vital, growing group should have more than one active person. In
troubled nonprofits, financial information is often tightly held by
someone who will not willingly relinquish monetary control. Ideally,
there should be <it>some</it> LUG duty rotation, including duties
@ -1232,33 +1226,68 @@ possible to publish these on the World-Wide Web.
<sect1>Elections, democracy, and turnover
<p>
Operating your LUG via democratic process is absolutely vital -- if and
Governing your LUG democratically is absolutely vital -- if and
only if you believe it is. I intend that remark somewhat less cynically
than it probably sounds, as I shall explain.
Tangible stakes in LUG politics tend to be minuscule to the point of
comic opera: There are typically no real assets, and differences can be
resolved by either engineering around them with technology (the Linux-ey
solution) or through the trivial exercise of setting up a parallel
effort (either in an additional LUG or otherwise). Moreover, even the
Tangible stakes at issue in LUG politics tend to be minuscule to the point of
comic opera: There are typically no real assets. Differences of view
can be resolved by either engineering around them with technology (the Linux-ey
solution) or by letting each camp run efforts in parallel. Moreover, even the
most militantly "democratic" LUGs typically field, like clockwork,
exactly as many candidates as there are offices to be elected -- not a
exactly as many candidates as there are offices to be filled -- not a
soul more.
It's tempting to mock such exercises, as form over substance, but such
is not (much) my intent (nor to claim irregularities). Rather, I
mention them to point out something more significant: Active volunteers
are vital, and should be encouraged. It seems likely that the
It's tempting to mock such exercises as empty posturing, but such
is not (much) my intent. Rather, I
mention them to point out something more significant: Attracting and
retaining key volunteers is vital to the group's success. Anything that
makes that happen is good. It seems likely that the
"democratic" exercise stressed in some groups, substantive or not,
encourages participation, and gives those elected a sense of status and
legitimacy. Those are Good Things.
encourages participation, and gives those elected a sense of status,
legitimacy, and involvement. Those are Good Things.
Thus, if elections and formal structure help involve active
participants, use them. If their absence helps attract participants,
Thus, if elections and formal structure help attract key
participants, use them. If those deter participants,
lose them. If door-prizes and garage sales bring people in, do
door-prizes and garage sales. Participation, as much as software, is
the lifeblood of your LUG.
The reason I spoke of "key" volunteers, above, is because, inevitably, a very few
people will do almost all of the needed work. It's just the way things go, in
volunteer groups. An anecdote may help illustrate my point: Towards the end
of my long tenure as editor and typesetter of San Francisco PC User Group's
40-page monthly magazine, I was repeatedly urged to make magazine
management more "democratic". I finally replied to the club president,
"See that guy over there? That's Ed, one of my editorial staff. Ed just
proofread twelve articles for the current issue. So, I figure he gets
twelve votes." The president and other club politicos were dismayed by my
of my work-based recasting of their democratic ideals: Their notion was that each
biped should have an equal say in editorial policy, regardless of ability to
typeset or proofread, or whether they had ever done iota to assist magazine
production. Although he looked quite unhappy about doing so, the president
dropped the subject. I figured that, when it came right down to it, he'd
decide that the club needed people who got work done more than they
needed his brand of "democracy".
But we weren't quite done: A month or so later, I was introduced to a
"Publications Committee", who arrived with the intent of doing nothing but
vote on matters of newsletter policy (i.e., issue "executive" orders to the
volunteer production staff). Their first shock came when I listened politely
to their advice but then applied my editorial judgement as usual. Much
worse, though: I also assigned them work, as part of my staff. Almost
all immediately lost interest. (Bossing around other people seemed likely
to be fun; doing actual work was not.)
The point is that the widespread urge to vote on everything is at best orthogonal
to any desire to perform needed work; at worst, the former serves as an
excuse to compulsively meddle in other people's performance of the
latter.
To sum up: Have all the "democracy" that makes you happy, but watching after
the well-being of your key volunteers is what matters. (To quote Candide,
"We must cultivate our garden.")
Last, plan for your replacement: If your LUG is a college student
group, and must go through a paperwork deathmarch every year to stay
accredited, make sure that and all other vital processes are documented,
@ -1296,10 +1325,9 @@ I welcome questions about and feedback on this document. Please send
them to me at <htmlurl name="rick@linuxmafia.com"
url="mailto:rick@linuxmafia.com">. <it>I am especially interested in
hearing from LUG leaders around the world</it>. I'd like to include
real-life examples of things described here. I'd also like to include
more on LUGs outside the USA, to reduce this HOWTO's residual
US-centrism. Please let me know of things your group does meriting
description here.
real-life examples of things described here. I'm particularly trying to
include more on LUGs outside the USA. Please let me know of
things your group does meriting description here.
<sect1>Document history
<p>
@ -1318,7 +1346,7 @@ description here.
donations and LUG political considerations.</item>
<item>1.6.1: Very minor additions.</item>
<item>1.6.2: Minor corrections.</item>
<item>1.6.3: Maintenance assumed by Rick Moen: General initial touchup,
<item>1.6.3: Maintenance assumed by Rick Moen: General initial touch-up,
correction of broken URLs, etc.
<item>1.6.4: Further minor fixes and additions.
<item>1.6.5: More-extensive edits, added "Limits of advocacy",
@ -1328,8 +1356,11 @@ tightening of phrasing, greater brevity in places.
<item>1.6.6: More small fixes, added Yahoo LUG list.
<item>1.6.7: Added formal-organisational pros/cons, "Elections,
democracy, and turnover" section, Web site suggestions, and link
to Recipe for a Successful Linux User Group" essay. Fixed mis-tagged
to "Recipe for a Successful Linux User Group" essay. Fixed mis-tagged
sections under "Legal and political issues".
<item>1.6.8: Fixed small glitches. Rewrote section concerning
Linux news outlets; parts of sections concerning consultants, businesses,
and elections.
</itemize>
@ -1343,9 +1374,9 @@ over and renovate his creation starting in 2003.
Warn regards and thanks to <url name="Chris Browne"
url="mailto:cbbrowne@cbbrowne.com"> for describing the situation with
non-profit and charitable groups in Canada, his thoughts on financial
donations as a way to participate in Linux and the free software
movement, and his ideas about the kinds of political issues likely to
arise within LUGs.
donations as a way to participate in Linux and the free software and
open-source software movements, and his ideas about the kinds of
political issues likely to arise within LUGs.
In addition, the following people have made helpful comments and
suggestions: