From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Liam Lindholm <liam.oskar.lindholm@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Richard Stallman: Why “GNU’S Not Linux” and Why We Should “Say LiGNUx”
Date: Mon, 23 Dec 2013 12:51:40 -0500 [thread overview]
Message-ID: <52B8782C.60901@gmail.com> (raw)
In-Reply-To: <CANq1nODU8QOLor0j8rTRdu+bRid9t5==pNdS0rZ-vZkg2hCrSQ@mail.gmail.com>
On 2013-12-23 12:01, Liam Lindholm wrote:
> Dear fellow Linux kernel hackers:
>
> It has come to my attention that Richard M. Stallman, founder of the
> Free Software Foundation and creator of the GNU project, has once
> again set out to fragment our grassroots community.
>
> Recently, Mr. Stallman has started a new push for acknowledgement of
> GNU in Linux. No, not the familiar “GNU/Linux” that we're all sick and
> tired of hearing about but, instead, a failed anagram of these same
> terms. The campaign is called “Say LiGNUx” and demands that users of
> any Linux-kernel operating system employing GNU software (which
> comprises less than 15% of most modern Linux distributions nowadays)
> call the operating system “LiGNUx.”
As much as I hate to point this out, that less than 15% comprises most
of the big mainstream distros (eg, Suse, Red Hat, Fedora, Debian,
Ubuntu, Gentoo, etc.).
>
> His presentation on the “Say LiGNUx” campaign is served in PNG format
> at http://imgur.com/a/beY7E so you can see the insanity for yourself.
[...snip...]
> Mr. Stallman even suggests that users who refuse to say LiGNUx should
> instead install GNU/HURD so as to remove any ambiguity about licenses
> and nomenclature. What the hell?!
I'd say that this is even stupider than the LiGNUx, Hurd only runs on
32-bit x86, doesn't support a large majority of modern hardware, and
trying to install it is comparable to trying to get a rebate from
Microsoft for not using a pre-installed copy of Windows.
>
> When is the last time someone named their operating system after the
> license the kernel is released under? Such an esoteric naming method
> is madness. Should Apple call OS X “Apple/XNU?” Or how about the
> Berkeley operating systems? Should they call their products “FreeBSD”
> or “OpenBSD?” Should Microsoft call their operating system “Microsoft
> Windows?” The suggestion is patently absurd.
>
> We should not give in to the wailing demands of this zealotry. Mr.
> Stallman clearly needs a break from promoting an increasingly
> irrelevant software platform. Perhaps that means banning him from
> LKML, or asking Linus to suggest some vacation therapy for poor Mr.
> Stallman and his zealotry, or having the Linux Foundation issue a
> press release distancing themselves from RMS, GNU, and the Free
> Software Foundation.
I'd personally say the press release is probably best. Mr. Stallman's
zealotry makes all free software developers look bad, yet he dosen't
seem to realize that.
next prev parent reply other threads:[~2013-12-23 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 17:01 Richard Stallman: Why “GNU’S Not Linux” and Why We Should “Say LiGNUx” Liam Lindholm
2013-12-23 17:51 ` Austin S Hemmelgarn [this message]
2013-12-24 11:55 ` Martin Nybo Andersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B8782C.60901@gmail.com \
--to=ahferroin7@gmail.com \
--cc=liam.oskar.lindholm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox