From: "Rubén Rodríguez Pérez" <ruben@es.gnu.org>
To: Alexandre Oliva <lxoliva@fsfla.org>
Cc: linux-libre@fsfla.org, libreplanet-discuss@gnu.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.28.8-libre1: suitable for Free System Distributions
Date: Sat, 21 Mar 2009 22:46:20 +0100 [thread overview]
Message-ID: <1237671980.30743.7.camel@thinkpad> (raw)
In-Reply-To: <or7i2i7g5u.fsf@livre.oliva.athome.lsd.ic.unicamp.br>
I'm going to backport it into Trisquel 2.1 (hardy based) immediately, it
seems to be an excellent work!
Also, a 2.6.24 deblobber based in this work would be very useful, as it
can be applied to the default kernel from both Trisquel and gNewSense.
Kudos.
Rubén
El sáb, 21-03-2009 a las 17:51 -0300, Alexandre Oliva escribió:
> Several months ago, I realized the existing releases of Linux-libre,
> that removed non-Free Software present in Linux, still retained code and
> documentation that induced users to install and use non-Free Software.
> This means it wasn't fit for use in Free System Distributions.
>
> I started working to fix that bug back then. Today, I'm very excited to
> announce, straight from the Libre Planet 2009 conference organized by
> the FSF, the first version of Linux-libre that won't do that any more.
>
> The 2.6.28-libre1 release, and the patched 2.6.28.8-libre1 release, are
> now available from http://linux-libre.fsfla.org/, bringing back several
> drivers that used to be disabled before, and not disabling any driver
> whatsoever.
>
> Some of the drivers we used to disable have been modified so that they
> now report the lack of Free firmware, instead of requesting users to
> load non-Free Software into their systems. These reports should be
> useful for userland to pick up and report some useful, informative and
> educational message to the user, explaining that their hardware is not
> compatible with Free Software.
>
> Other drivers we used to disabled contained suspicious strings that had
> been conservatively removed. Having verified the technical and legal
> status of some of them, and having determined that some others weren't
> code after all, this release brings them back in. Some WiFi interfaces
> and video capture devices, will be functional with this new release.
>
> Other releases of Linux-libre, including past ones and the upcoming
> 2.6.29, will certainly require additional work, but nothing even close
> to the amount of work it took to get to this one. Thanks for your
> patience.
>
> I'd also like to thank the FSF for offering us our new build and web
> server, the first in which this release was prepared, and Jeff Moe, who
> had paid for our previous server.
>
> Please report to linux-libre@fsfla.org any problems you run into with
> this release (other than compile errors in a few dvb drivers, I'm on
> those already), and let us know of any case in which you believe I may
> have removed something that could have been retained.
>
> Happier (and freer) hacking, :-)
>
prev parent reply other threads:[~2009-03-21 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 20:51 linux-2.6.28.8-libre1: suitable for Free System Distributions Alexandre Oliva
2009-03-21 21:46 ` Rubén Rodríguez Pérez [this message]
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=1237671980.30743.7.camel@thinkpad \
--to=ruben@es.gnu.org \
--cc=libreplanet-discuss@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-libre@fsfla.org \
--cc=lxoliva@fsfla.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