About this file
===============
Here it is, probably the last release of Alchemy before the public version.
I removed the tags to protect my suppliers who made this happen - thanks a lot to them!
As usual, use with care since it is a prerelease version and might be buggy.
Do NOT contact Sveasoft about problems with this release as they only give support to paying subscribers.
This firmware is for WRT54G V1.0, V1.1, V2.0, V2.2 and WRT54GS V1.0, V1.1 routers only.

How to flash
============
For a safe flashing process do this:
1) Reset router to factory default (optional: backup settings before this step)
2) Flash bin file to router via web interface (some say renaming to code.bin helps)
3) Reset router to defaults again
4) optional: restore the backup you made in 1)
If anything goes wrong, check the forum. It has detailed instructions for router recovery and people there can help you.

GPL Stuff
=========
I'd like to clear up some GPL-related stuff at this point.

1) The (re-)distribution of this firmware is completely legal, no matter what Sveasoft says.
   They have a list of non-GPL components in their FAQ but just because something isn't GPL doesn't mean it can't be redistributed.
   Check this thread for license details: http://forum.bsr-clan.de/viewtopic.php?t=783

2) Sveasoft is in clear GPL violation for not releasing source code or a written offer alongside the binaries
   The GPL requires one to either distribute source code with the binaries or add a written offer for it.
   Sveasoft does neither, they just release source code a couple of months later to cover their a$$.

3) Sveasoft is in clear GPL violation for not giving "any other recipients of the Program a copy of this License along with the Program."

4) Sveasoft is in clear GPL violation because the source code provided (with delay) does not compile to the binary delivered
   This obviously is the case since the source code does not contain the tagging system.
   In particular, the files /www/image/UI_Linksys.gif, /etc/.reg (and more) differ in each distributed binary

5) Sveasoft's next GPL violation is coming up: an activation system in the Talisman release
   If this will not be reflected in the source code (which would render it useless), there really should be a reaction from the FSF
   
Speaking of which, I am shocked that to this date, no one from the FSF noticed Sveasoft's clear GPL violations.
I am not even going to list the countless offenses Sveasoft did against the open source community, just take a look at this for a smile:
http://www.chillingeffects.org/dmca512/notice.cgi?NoticeID=1471

Closing comments
================
Let's hope Sveasoft finds a way to make money without ripping of GPL products.
Don't get me wrong, nothing is wrong with making money of a GPL product, but not like this.
Not through harassment, lies, defamation and GPL violations.

Enough talk, now have fun with this tagfree firmware,
TheIndividual

For news and links to my mirrors, visit my slashdot journal at http://slashdot.org/~TheIndividual/journal/
Post comments, questions or anything else at http://forum.bsr-clan.de/viewforum.php?f=12