Slashdot Mirror


Linksys Releases GPLed Code for WRT54G

petree writes "I stumbled across this on the Linksys website. Linksys has apparently caved to community pressure and released the GPLed source for linux running on their WRT54G. Cool Beans!"

335 comments

  1. Nice, but not a ton of info from it. by draziw · · Score: 3, Interesting

    It's nice that you can see the GPL bits running on their box (Hey running a 2.4.5 kernel) - but it doesn't give you drivers, or scripts, etc. :(

    No I don't think they need to provide the other bits, but it sure would be nice to get some 802.11 drivers, etc.

    --
    +1 Karma bonus due to GPL Love & Low User ID.

    1. Re:Nice, but not a ton of info from it. by 1010011010 · · Score: 4, Insightful

      Yes, it would be nice to get the "Secret bits," like drivers, but this is actually better for the community in the long run. Why? Because Linksys will have released the GPL parts publically, without losing control of their "I.P." or the "I.P." of companies providing components for this product (if any).

      "Viral" GPL gobbling "I.P." like pac-man with melanoma? Not really!

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    2. Re:Nice, but not a ton of info from it. by Anonymous Coward · · Score: 5, Insightful

      Agreed. It makes good engineering sense too. By leaving the kernel unmodified, it removes a maintenance headache. Engineers can design their IP to interface with the kernel in the standard way. The kernel then becomes a "black box" and is decoupled from the internals of the company's IP. It allows for a more modular and maintainable design.

    3. Re:Nice, but not a ton of info from it. by Daniel+Phillips · · Score: 4, Insightful

      It's nice that you can see the GPL bits running on their box (Hey running a 2.4.5 kernel) - but it doesn't give you drivers, or scripts, etc.

      The original flash image was decoded (by Andrew Miklas) as a cramfs filesystem. We have *all* the components available in binary form. Unless there is crytographic checking in the bootloader (i.e. a signed flash image) we're all set to go make our own images complete with Linksys's proprietary binaries and our hacked/improved GPL binaries.

      To my knowledge, nobody has done this yet. I hope that doesn't last long. These units will make lovely general-purpose embedded machines if we can put our own code in them. We'd have to rely on Linksys binaries for some of the hardware, but personally I have no ideological problem with that. What I want is to be able to fix some bugs of the bugs and interface stupidities in the darn thing, and to add some of my own functionality, such as being able to ssh into it. Of course, I'd like it even more if Linksys released the full hardware specs, but hey. It's a start.

      Now, I see the kind of hacking I described above, and which I fully intend to get involved in, as nothing but good for Linksys. If it turns out we can reflash the unit as it appears we can, I for one will be in the market for a few more of these.

      --
      Have you got your LWN subscription yet?
    4. Re:Nice, but not a ton of info from it. by Anonymous Coward · · Score: 0, Troll

      And this is exactly why companies should stay the hell away from Linux - the pirate mentality that goes with it.

    5. Re:Nice, but not a ton of info from it. by Anonymous Coward · · Score: 0

      Why? I bought it, so I should be able to do whatever I want with it. In-fact, I'm going to buy it, because I CAN do whatever I want with it!

      The hell with the warranty, and to hell with their support - once I open the box, it's my problem. I'll do what I want with this system, because it's mine!

    6. Re:Nice, but not a ton of info from it. by Christopher+Thomas · · Score: 4, Insightful

      And this is exactly why companies should stay the hell away from Linux - the pirate mentality that goes with it.

      This is using Linksys software on the Linksys hardware that it was provided with. How is it copyright violation?

    7. Re:Nice, but not a ton of info from it. by noda132 · · Score: 1, Informative

      Yes, it would be nice to get the "Secret bits," like drivers, but this is actually better for the community in the long run.

      This simply doesn't make sense. Large corporations hoarding "IP" is not better for the community. Unless your definition of "community" is "Linksys." Even then, it may be better for Linksys itself if it'd release 802.11g drivers. I know that I for one would buy one of their cards if they did, and since they don't I won't.

      What I want, and what I know many other people want, is an 802.11g driver. Linksys has one. They choose not to release it? Not even with a proprietary license and without support, à la nVidia? I simply cannot see how that is better for the "community."

    8. Re:Nice, but not a ton of info from it. by GrenDel+Fuego · · Score: 1

      I'm not sure if anyone else noticed this, but that does not appear to be a stock 2.4.5 kernel. I ran a diff, and it came up as 14MB. Perhaps something interesting has been added?

      (Note that I'm not too familiar with recursive diffs, so it's possible I did something wrong)

    9. Re:Nice, but not a ton of info from it. by BJH · · Score: 2, Interesting

      Since it's not likely that Linksys have added 14MB worth of changes to the kernel, I'd say you've done something wrong.

    10. Re:Nice, but not a ton of info from it. by kasperd · · Score: 2, Interesting

      How is it copyright violation?

      I don't think it could possibly be a copyright violation. Linksys more or less have to allow it, otherwise I think they could be in violation with the GPL on the kernel and some of the other stuff they are using.

      --

      Do you care about the security of your wireless mouse?
    11. Re:Nice, but not a ton of info from it. by Anonymous Coward · · Score: 2, Interesting

      Okay, but without drivers for that wireless hardware (which is closed and proprietary), you've got yourself a nice little doorstop to hack at your own will...

      Seriously. What good is a WIRELESS ROUTER without WIRELESS SUPPORT. That's why we shouldn't particularly care about hacking most of this thing. Now, if you can hack it to be better at what it currently does, then more power to you... Since the source of the non-closed parts were already available, I don't see that as much of a problem.

      Does this product support IPV6, for example? If not, it would be interesting to just do a couple recompiles and see if we can make it do so.

    12. Re:Nice, but not a ton of info from it. by jjackson · · Score: 5, Insightful

      RIGHT... because nobody ever hacks, cracks, or pirates stuff on Windows. Never mind the fact that the most widely pirated piece of software in existance is Windows itself.

      Provided you are modifying the unit for your own purposes and not redistributing the Liksys binary code, how exactly does this qualify as pirating?

      Personally, I run my business on Linux and have implemented it in several companies where the Linux system itself was replacing a pirated copy of Linux.

      I can only assume you are trolling here...

    13. Re:Nice, but not a ton of info from it. by oohp · · Score: 5, Insightful

      Pirate mentality? If I buy a car I could disassemble it and change some components, right? How is this pirating?

      They should've used NetBSD if they don't like the GPL and releasing the source.

    14. Re:Nice, but not a ton of info from it. by kasperd · · Score: 2, Informative

      Since it's not likely that Linksys have added 14MB worth of changes to the kernel, I'd say you've done something wrong.

      There is nothing wrong with the test he performed. I tried the same and got a 14.3MB patch. But though there is this amount of changes, I don't believe Linksys wrote it all. In particular I noticed a lot of XFS stuff. It could be that Linksys is really using a different kernel version and just changed the version number to match a closed source driver, they didn't want to recompile. Or it could be that Linksys has applied third party patches. So who is going to search for the kernel version resulting in the smallest diff. I tried with kernel version 2.4.6, which resulted in a larger patch, so it is probably not just a later version.

      --

      Do you care about the security of your wireless mouse?
    15. Re:Nice, but not a ton of info from it. by jjackson · · Score: 3, Informative

      Err... make that a pirate copy of Windows not *Linux*. Must have been that Linux pirate mentality :)

    16. Re:Nice, but not a ton of info from it. by Ian+Jefferies · · Score: 1

      Personally, I run my business on Linux and have implemented it in several companies where the Linux system itself was replacing a pirated copy of Linux.

      I assume you mean Windows :)

      Ian.

      --
      A physicist is an atom's way of thinking about atoms
    17. Re:Nice, but not a ton of info from it. by R0 · · Score: 1

      Unless your definition of "community" is "Linksys."
      Like the Linksys Communtiy network?

    18. Re:Nice, but not a ton of info from it. by fmu · · Score: 1

      IP != trade secrets, which is what you probably meant

      you are welcome.

    19. Re:Nice, but not a ton of info from it. by Daniel+Phillips · · Score: 1

      Okay, but without drivers for that wireless hardware (which is closed and proprietary), you've got yourself a nice little doorstop to hack at your own will...

      The drivers probably take the form of kernel modules. (The only other alternatives are user space programs - very unlikely - or code linked into the kernel, in which case it has to be GPLed.) So we can continue using those modules, as long as we stick with the 2.4.5 kernel version they're using (sick, I know). We could possibly even write shims to forward-port the binary modules to later kernel versions, if there turned out to be enough interest.

      So we're not stuck for drivers, sorry for assuming that everybody would see that right away.

      --
      Have you got your LWN subscription yet?
    20. Re:Nice, but not a ton of info from it. by bensonandhedges · · Score: 1

      The driver on My Belkin is wl.o the Broadcom chip has an integrated MIPS3000 core so the binary driver is in MIPS assembler objdump wil disassemble it it is pretty easy to pick out the calls mades to the card....... We could do a simple open source driver in weeks......

    21. Re:Nice, but not a ton of info from it. by Anonymous Coward · · Score: 0

      I did see it right away. I was refering to the driver breakage in Linux. Even a slight recompile of 2.4.5 could break those drivers. So let's say you are saying, "Linux, sick, man! Let's compile 2.5.x and give it GNOME!" Well, I'm sure you realize how unrealistic that is. But then, seems every rabid fool wants to do something like that with their Linux-based toaster, or whatever.

    22. Re:Nice, but not a ton of info from it. by ryanr · · Score: 1

      They're kernel drivers, I believe:

      \lib\modules\2.4.5\kernel\drivers\net\diag\diag. o
      \lib\modules\2.4.5\kernel\drivers\net\et\et.o
      \lib\modules\2.4.5\kernel\drivers\net\mac\writemac .o
      \lib\modules\2.4.5\kernel\drivers\net\wl\wl.o

      Not ideal (open-source drivers would be nice) but workable, for this hardware platform. They are binaries for a custom MIPS32 processor after all. But yes, if want you want to do (like me) is make small mods to the box, these drivers are what you need to stay functional.

    23. Re:Nice, but not a ton of info from it. by johnnyb · · Score: 1

      No, they can put any license they want on their binary-only drivers.

  2. Does this mean we can work on the firmware? by fishynet · · Score: 5, Interesting

    Can the OSS community now modify the firmware and make custom things for it?

    --

    Cats: All your base are belong to us.
    Captain: Take off every sig !!
    1. Re:Does this mean we can work on the firmware? by Anonymous Coward · · Score: 1, Interesting

      You rube! I would bet that these are not even the real packages that are used on the router. Do a diff against the original released packages. I will bet that there are no differences. Would believe that these packages go into a commercial product with *NO* fixes at all?

      Linksys has just released the original GPL packages that they used -- no workarounds or enhancements for running on the broadcom chips.
      You couldn't recompile the linksys router platform from this in a million years. And until someone with a ton of money actaully takes this to court, there is not a thing you can do about it except jump up and down and stamp your feet.

  3. New linux toy? Oh yeah by petree · · Score: 4, Interesting

    Now that all of this has been released, I wonder if we will be seeing alternative firmwares with support for new features (detailed external logging, radius server, wireless VLANs like the cisco APs, traffic shaping, oh, and MeshAP could be cool too.) A friend of mine already bought his WRT54G and likes it, but after I found this out (and submitted the story to slashdot) I ordered mine from Amazon($130 with free shipping) along with the NetGear WAG511($85 - 802.11a, 802.11g, 802.11b) as recommended by a Toms Hardware review. I'm so excited that I am going to have a dope 54mbps wireless network in my dorm room for only $215. A little excessive, maybe, but hey I will probably keep this for another 5+ yrs. Especially the 802.11a 802.11g cardbus card. Oh hey, if you are shopping, check out the SeattleWireless Hardware Comparison. They have all sorts of info there and it made it easier to decide what to buy.

    1. Re:New linux toy? Oh yeah by Anonymous Coward · · Score: 0

      " I'm so excited that I am going to have a dope 54mbps wireless network in my dorm room for only $215."

      Try a 1000mbps cat5e cable. 20' for $5 is a good price.

    2. Re:New linux toy? Oh yeah by NiteEyes · · Score: 0

      Cat5e is only good to around 350 Mbits I believe...

      --
      -- Creativity knows no medium
  4. What about the BEFW11S4? by SirDrinksAlot · · Score: 4, Interesting

    Isnt the BEFW11S4 in the same boat as the WRT54G? Isnt it based on linux as well?

    1. Re:What about the BEFW11S4? by eggboard · · Score: 1

      The BEFW11S4 is based on a different chipset: the Intersil Prism stuff, not Broadcom's 802.11g chips. I'm not sure about the internals, but I doubt the software on the one will run the other as they're entirely different underlying components. (I don't know about processor, etc., but I believe Broadcom created a reference design, like Intersil, so it's likely to be 100 percent different.)

      --
      Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others
    2. Re:What about the BEFW11S4? by SirDrinksAlot · · Score: 1

      You missed my point entirely, The operating system on the BEFW11S4 is Linux as well. The wireless chipset has nothing (well verry little) to do with what OS is being run on the Router.

  5. Ah, Linksys by Anonymous Coward · · Score: 4, Funny

    They're too lazy to code proper, secure solutions for their products, so they send it to the OSS community to do.

    1. Re:Ah, Linksys by Anonymous Coward · · Score: 2, Insightful

      A company makes hardware, they don't release software & driver code to public.

      People say they are an evil corporation trying to hide their secrets and prevent users of rare operating systems from using their product.

      A company makes hardware, they release software & driver code to public.

      People say they want others to do their coding.

      You just can't win can you?

    2. Re:Ah, Linksys by Anonymous Coward · · Score: 0

      But it's Linksys. Linksys equipment is universally known to be cheap in price and woefully insecure. Maybe if they had a better track record, it wouldn't be a lose lose situation

    3. Re:Ah, Linksys by Anonymous Coward · · Score: 0

      As opposed to buying an insecure windows?
      Sounds like these guys got smart. Low cost, High security, and marketable.

    4. Re:Ah, Linksys by RAMMS+EIN · · Score: 2, Insightful

      Which is a Good Thing, actually. Everybody should do what they do best. Linksys is good at making hardware, so let them do that. Open source hackers are good at writing software, so let them do that. All companies have to do is enable those hackers to code for their products, and they'll get all sorts of stuff for free. Company happy, hackers happy, and end-users happy, because they can rest assured that the products can be supported even after the original creator stops supporting them (or never supports them in the first place).

      --
      Please correct me if I got my facts wrong.
  6. Next stop: Drivers by InfiniterX · · Score: 2, Interesting

    Hopefully this means that they'll release drivers for their 54-mbit cards already, then.

    From what I read, they use the same Broadcom chipset as the access points, which means Linux drivers do exist, in spite of their not being released to anyone.

    1. Re:Next stop: Drivers by fdawg · · Score: 1

      That would imply that they used a stock pci/isa bus. In my experience, the chips may be the same in an application specific device as well as a standard PC peripheral, but the lack of a standard bus would make it (MUCH!) harder to reverse engineer a driver.

      It would be very interesting if it was a stock bus.

    2. Re:Next stop: Drivers by Anonymous Coward · · Score: 0

      In my experience, most of these devices just use OTS parts. Crack the case open and see what they put inside.

    3. Re:Next stop: Drivers by tigga · · Score: 2, Informative
      Hopefully this means that they'll release drivers for their 54-mbit cards already, then.

      There are drivers: http://sourceforge.net/projects/madwifi/ and ath driver for FreeBSD.

    4. Re:Next stop: Drivers by Anonymous Coward · · Score: 0

      The Linksys box uses the Broadcom chipset, not the competing Atheros chipset.

      Broadcom haven't released drivers, though they obviously exist as they're in a lsmod from the Linksys box. Thus the interest.

      BTW, Linksys seems to have dropped off DNS, either because of, or to prevent, slashdotting.

      To cut to the chase. Is the source for the Broadcom chipsets included in the Linksys source release. Can anyone who has downloaded the code tell us?

    5. Re:Next stop: Drivers by geirt · · Score: 1

      >To cut to the chase. Is the source for the Broadcom chipsets included in the Linksys
      >source release. Can anyone who has downloaded the code tell us?

      I have looked at the kernel source code, and I can't find any drives. The kernel isn't a plain 2.4.5, there seems to be many patches (arch, drivers, net, xfs, mtd, etc). But no Broadcom drivers.

      --

      RFC1925
    6. Re:Next stop: Drivers by bensonandhedges · · Score: 1

      The driver is wl.o contained in the firmware i have disassembled it back into MIPS3000 assembler and I'm starting an open source driver tonight

    7. Re:Next stop: Drivers by Anonymous Coward · · Score: 0
      i have disassembled it back into MIPS3000 assembler and I'm starting an open source driver tonight


      Suuuuure you are...uh huh. That's likely to work...not.

    8. Re:Next stop: Drivers by bensonandhedges · · Score: 1

      I don't get you... why wouldn't this work, it's hard yeah but not impossible....

      here is the card reset function

      000013f0 :
      13f0: 27bdffe8 addiu sp,sp,-24
      13f4: afbf0010 sw ra,16(sp)
      13f8: 3c020000 lui v0,0x0
      13fc: 24420000 addiu v0,v0,0
      1400: 0040f809 jalr v0
      1404: 8c840004 lw a0,4(a0)
      1408: 8fbf0010 lw ra,16(sp)
      140c: 00001021 move v0,zero
      1410: 03e00008 jr ra
      1414: 27bd0018 addiu sp,sp,24

    9. Re:Next stop: Drivers by ryanr · · Score: 1

      My copy of IDAPro is the standard edition, not advanced, so unfortunately, I can't use that tool to disassemble MIPS. What tool(s) are you using?

    10. Re:Next stop: Drivers by bensonandhedges · · Score: 1

      objdump from binutils compiled under gentoo (feel the power!!) with --enable-targets=all..... the --source option doesn't seem to work, I don't know if the objdump build is the problem or the compiled object.... or the fact I have just discovered... that the gcc compiler they are using has been modified.....

      All in all this angers me.. broadcom used linux becasue it was cheaper that QNX or homegrown and it did exactly what they wanted it to do... they also had no intention of releasing user linux drivers even in binary form becasue of the risk of them being hacked (objdump) or to maintain a revenue stream....

      The truth is that a) they are not playing fair on this one and b) they might never use linux again because of the hassle...... There is no doubt that they are making a bunch of money out of this 4710 chip and 99% of the code that is running on it is due to the hard work of us GPL'ers....

      They deserve to be punished for this but if we even make a move towards reverse engineering the laws in the good 'ol US of A will have us hung, drawn and quatered before we can say shareholder profit....

      I actually have a very strong view on what needs to be done..... ask me if you dare.....

  7. Finally by rkz · · Score: 2, Insightful

    I was vary suprised that there wasn't a huge uproar when this was coverd on /. earlier.
    If they had not released the source would buy their products again, to be honest I certainly would because they are the cheapest.
    If you would not, does their decision to release the source change your mind?

    1. Re:Finally by noda132 · · Score: 2, Insightful

      If they had not released the source would buy their products again...

      If they had not released the source, they would be breaking the law. The world is still holding its breath for the first case of the FSF kicking ass in court.

    2. Re:Finally by Namaseit · · Score: 1

      "If you would not, does their decision to release the source change your mind?"

      Well i already have an 802.11b card of theirs - WPC11 v4.0 but now that they have released the source of this I would have to say this is a big plus and will most likely swing my networking purchases in their favor.

      --
      75% of all statistics are made up!
  8. And now what? by ObviousGuy · · Score: 5, Funny

    Are you going to go build your own router?

    Are you going to comb through the code only to find that it's not that much different from the other code you never look at?

    Face it, if it some source is vital to your company staying competitive, it isn't going to be GPL'd.

    --
    I have been pwned because my /. password was too easy to guess.
    1. Re:And now what? by ryanr · · Score: 4, Funny

      No, I'm going to load strange software on it, and make it do things that have little or no practical value.

      Because I can.

    2. Re:And now what? by Anonymous Coward · · Score: 0

      I'm going to load strange software on it, and make it do things that have little or no practical value.

      You wouldn't happen to be the progeny of Steven Pinker, would you?

    3. Re:And now what? by Xerithane · · Score: 1

      Are you going to go build your own router?

      As the geeks laid out their plans for routers that give health reports in a sexy female voice, they realized that the only thing that was GPL'd was the only slightly modified kernel, which they had always had.

      --
      Dacels Jewelers can't be trusted.
    4. Re:And now what? by Anonymous Coward · · Score: 0

      Maybe DLink will release the hardware with no firmware on it so we can create our own and load it up. Imagine it without the MS Tax...er...

    5. Re:And now what? by Felinoid · · Score: 1

      Face it, if it some source is vital to your company staying competitive, it isn't going to be GPL'd.
      Only if your selling the software and not giving away (as any and all hardware venders do)
      When your selling software you want as many people buying your software as possable. Giving it away and worse GPLing the source is counter productive.
      When you sell HARDWARE you want as many people buying your HARDWARE as possable. Giving away the SOFTWARE that makes it run is a good idea. GPLing the source is even better.
      Great you have closed source Windows drivers horray for you becouse you can sell to 75% of the market like everyone else.
      Thats ok but just by GPLing the code they go from 75% to 100%... and byond as hackers and hams find new uses for them.
      Some hams have reprogrammed some communications hardware to do new things. I'd be neat if a WIFI card can also be a packet modem or a repeater.
      Maybe even a self contained wifi repeater for those community network projects.
      Who knows?

      --
      I don't actually exist.
  9. A wireless network. For a dorm room. by rob-fu · · Score: 4, Insightful

    I'm so excited that I am going to have a dope 54mbps wireless network in my dorm room for only $215. No offense, but I think your money is better spent elsewhere :) How big can your dorm room possibly be to the point where 54mbs wireless would be necessary?

  10. So... by Erwos · · Score: 1

    Does this give out any cool new code, or is it just simple modifications of the kernel? I'm guessing it's just a few minor changes to enable it to run on the router.

    Hopefully all of this commotion has not dissuaded Linksys from using the Linux kernel (in an appropriate fashion) in their future products.

    -Erwos

    --
    Plausible conjecture should not be misrepresented as proof positive.
  11. Its nice to see by Crashmarik · · Score: 4, Insightful

    It's really great to see a company that saw it had made a mistake, corrected it and moved on. My only wish is that more companies would take that attitude.

    1. Re:Its nice to see by Anonymous Coward · · Score: 1, Funny

      But for their delay, they're getting a right good slashdotting on the weekend!

  12. Cool Beans? by aaron240 · · Score: 5, Funny

    What is this, 1988?

    Is it also "rad" that the code was released?

    My apologies, I'm on a tear today. Hella has to go the way of "cool beans", but it looks like these things never die. *sighs*

    1. Re:Cool Beans? by phatman808 · · Score: 0

      Dude, that comment was totally bitchin'! ouch. sorry.

      --


      --
      Hwa!
    2. Re:Cool Beans? by Anonymous Coward · · Score: 0

      Fucking-A. Totally dudical comment, bro.

    3. Re:Cool Beans? by Qzukk · · Score: 1

      All your undying phrases are belong to us!

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    4. Re:Cool Beans? by Anonymous Coward · · Score: 1, Funny
      What is this, 1988?
      Yes.

      Now, if you'll excuse me, I need to adjust my mullet.

    5. Re:Cool Beans? by sharkey · · Score: 1
      Hella has to go the way of "cool beans"

      Don't diss da phrases, foo', or you gonna get tossed!

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    6. Re:Cool Beans? by appleLaserWriter · · Score: 1
  13. Never enough, though. by PaulK · · Score: 1, Interesting

    Now all I need is open source drivers for the 54g PCI and PCMCIA.

    I use one of these access points; my first network nmap after installing it was disconcerting. I had thought that someone was war driving, when I found the 2.4.5 -O.

    The last thing I expected to find was a Linux kernel.

    At least they had the __________ to step up and honor the GPL.

  14. Mod parent up by LittleLebowskiUrbanA · · Score: 1

    Good question. There's quite a few of these out there and this would benefit quite a few /.ers.

  15. 802.11g *nix drivers by Anonymous Coward · · Score: 0

    Hey, are there any drivers for the linksys/dlink 802.11g cards out there for *nix? I found a couple for a flavor of the 802.1a that were built for linux, but it seems that the *nix crowd is out of luck with high speed wireless :-/
    I have used this AP since late December and it rocks.

    1. Re:802.11g *nix drivers by KiloYankee · · Score: 5, Informative

      There's beta drivers from Atheros that supports 802.11g. Check it out. http://sourceforge.net/projects/madwifi/

  16. Not the full OS by KentoNET · · Score: 3, Informative

    Linksys only released the GPL pieces of what's running on that router. The way it looks, they haven't really put out anything that would help much to create a customized ROM for that device (web frontend specs, scripts, etc.). This isn't that much of a move for them, as it appears they've only released info of what they used, as well as a centralized location for exactly what GPL software is on their router.

    --
    "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    1. Re:Not the full OS by psyconaut · · Score: 5, Insightful

      Did you really expect them to release proprietary intellectual property?

      They complied with the GPL...they weren't required to do anything else, nor should a commercial enterpise be expected to do more if it doesn't aid their business.

      -psy

    2. Re:Not the full OS by wfberg · · Score: 1


      They complied with the GPL...they weren't required to do anything else, nor should a commercial enterpise be expected to do more if it doesn't aid their business.


      Although, perhaps it would aid their business. It's not like they're in the business of selling hardware at a loss only to make up for it in software sales like the console makers.. Software from third parties only adds to the value of their bricks, and you can bet your ass that their warranty excludes any hacking of the things anyway, so there are no extra support costs asociated to allowing others to hack the thing.

      Drivers etc. don't even have to be supplied in source code to bake a ROM; object code will do. So competitors won't get to see any more of their secret sauce then they get to see now.

      --
      SCO employee? Check out the bounty
    3. Re:Not the full OS by KentoNET · · Score: 1

      Exactly. And as I stated, even specs to certain things would do (like the web frontend, for backup purposes). That could be useful for adding or removing servers to or from the system and still having it be functional with parts of the system that aren't openly distributed. Unfortunately, such a thing would probably never happen.

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    4. Re:Not the full OS by psyconaut · · Score: 2, Insightful

      I design embedded systems.....and I can tell you that the last thing you want to do is to make it even easier to reverse engineer stuff. Things are bad enough as it is ;-)

      Plus, if people were able to reprogram the unit, I'm not sure how that'd really help the community. You'd probably see a bunch of people doing silly "hacks" with the system and a bunch of confused users not knowing what "distribution" to run on their Linksys access point.

      -psy

    5. Re:Not the full OS by palp · · Score: 1

      Yes, but software features are the main difference between brands of routers. Most of them have very similar hardware, and it's the configuration software that makes one better than the other, more often than not, especially to the average consumer. Give away the software for things like their web frontend, and all the features it offers, and they lose their uniqueness.

      --
      -palp
    6. Re:Not the full OS by NetJunkie · · Score: 2, Informative

      They don't want you to hack their boxes and add cool features. They want you to buy their next product which will include those features.

    7. Re:Not the full OS by Anonymous Coward · · Score: 0
      [...]proprietary intellectual property[...]

      Looks like you've been owned too much by the IP system.

      ...
      Ok, I'm ready, bring on the tomatoes.
    8. Re:Not the full OS by cyberformer · · Score: 2, Insightful

      They don't have to, but it would have been nice!

      Several companies have released (under GPL or otherwise) software that they don't legally have to. Apple (Darwin) is a prominent example.

    9. Re:Not the full OS by 73939133 · · Score: 1

      That argument falls flat because that's not how Linksys is selling their gateways. So far, they have had one model in each category, they have provided updates for it, and they have come out with new models only when a new networking standard has come out.

      And their development group is barely capable of producing a working wireless router as is. If they released the sources, people could fix their bugs and build new, interesting services with it.

      That would mean selling a lot more boxes, instead of what is happening now: my Linksys AP is stuffed into a closet because its software was too flaky.

    10. Re:Not the full OS by runderwo · · Score: 2, Insightful
      Plus, if people were able to reprogram the unit, I'm not sure how that'd really help the community. You'd probably see a bunch of people doing silly "hacks" with the system and a bunch of confused users not knowing what "distribution" to run on their [Linksys access point].
      Replace "Linksys access point" with "computer", another term that accurately describes the unit. See the problem? Thing is, people like things they can play with, and other people like those people to play with those things, because innovative stuff comes out of it in the end.

      How else is Linksys going to distinguish itself from the rest of the Taiwanese crowd?

    11. Re:Not the full OS by psyconaut · · Score: 1
      "How else is Linksys going to distinguish itself from the rest of the Taiwanese crowd?"

      Don't forget that Linksys is an Americancompany...so they're differentiating themselves from the "Taiwanese crowd" not the "rest of the Taiwanese crowd". ;-)

      Also, based on the analog that people like to play with things and the Linksys is an embedded computer system, then you can take that to the Nth degree and start asking Ford to provide you with the ECU firmware for your SUV, or asking LG to provide you with the firmware for the PIC microcontroller in your microwave so you can reprogram the display to say "Hello, Dave..."....and....and....get my drift? -psy

    12. Re:Not the full OS by Anonymous Coward · · Score: 0

      Possible, but why? wouldn't it be easier to release the driver binaries etc with kernel version independant code wrappers etc, and then sit back, watch and see which features people take the time to add? That way they know what features people want, and can add them to their next version. Simplified market research and someone else to do a lot of the developement stuff too. -- Cheaper, faster etc.

    13. Re:Not the full OS by kasperd · · Score: 2, Interesting

      they weren't required to do anything else

      From the GPL: For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.

      Now what I miss is the .config file for their kernel. I'm not sure if that is a requirement from the statement above.

      --

      Do you care about the security of your wireless mouse?
    14. Re:Not the full OS by ocelotbob · · Score: 2, Interesting
      and a bunch of confused users not knowing what "distribution" to run on their Linksys access point.

      I call bullshit on this one. Most users will go about their merry day not caring about what their AP runs, because they don't need to. TiVOs run Linux, have a vocal hacking community, and do you see the average TiVO user thinking about distros? No. This allows those people that want to play with their hardware a bit larger of an opportunity to do so. Giving their kernel patches back to the community just makes sense.

      --

      Marxism is the opiate of dumbasses

    15. Re:Not the full OS by Anonymous Coward · · Score: 0

      Almost everything in Darwin was open source to begin with. Woo, be still my heart.

    16. Re:Not the full OS by Ben+Hutchings · · Score: 1

      It's a valid shell script (though it's not always parsed by the shell) that controls compilation, so yes it is a requirement.

  17. Come out of the closet by poptones · · Score: 4, Insightful
    For one one-hundredth that price you could have bought twenty feet of cat-5, which would have given you 100mbps networking in that dorm room.

    I bet you like playing raquetball in the closet, too, don'tcha?

    1. Re:Come out of the closet by Zakabog · · Score: 0

      Yeah cause cat-5 cable is so much better than wireless

      1 - You can trip over it (which usually drags your laptop along for the ride or rips out any network cards attached to the cable, or destroys the ends of the cable, which can be a lot of fun)
      2 - You can only use it in a 20' radius as long as their is nothing blocking the wire
      3 - Wires can get caught on things so when you walk to your bed carrying your laptop, the wire can get snagged and well since you're still walking the laptop gets yanked out of your arms and falls to the floor, which is always a great thing.

      Ok that's enough sarcasm for now. I've wanted a wireless network for the longest time, I have a 5 port switch sitting on my floor that has people stepping on it all day. The only reason it's on the floor is cause the wires aren't long enough to reach it from all of my computers. If I had a wireless network for the computers that are too far away from my switch, I wouldn't have to worry about tripping over my switch. And I want to provide access to my cable modem for my aunt who lives on the first floor, I have a very large house and I'd need over 100' of cable to reach her computer (and that's if I drill through my floor and her roof.) If I had a wireless network I'd be able to easily setup a connection without any drilling or wires running through my whole house.

    2. Re:Come out of the closet by Anonymous Coward · · Score: 0

      I have a 5 port switch sitting on my floor that has people stepping on it all day. The only reason it's on the floor is cause the wires aren't long enough to reach it from all of my computers.

      Dude, how the hell large is your room?

      You do know that ethernet can run 100 meters, don't you? Why not just spend another $5 and get longer cables?

      I have a very large house and I'd need over 100' of cable to reach her computer (and that's if I drill through my floor and her roof.)

      First, 100' of cat-5e cable would cost you a grand total of $9. Second, you don't know very much about running cable... it's very rare to have to drill through ceilings/floors (especially in a residential house).. how do you think the electrical wires get both to you and to her? (Or do you think that uses wireless as well?)

    3. Re:Come out of the closet by Anonymous Coward · · Score: 0

      Dude, how the hell large is your room?

      Quite large, but there's more than one room in my house and a few other rooms have computers

      how do you think the electrical wires get both to you and to her?

      They were put their before the walls were put up, and they run BEHIND the wall, ethernet cable has to exit the wall somewhere (which would require drilling.) Maybe I can buy an ethernet faceplate thing and hook up wire to that but how much easier would it be to just buy wireless cards? I can spend hours setting up wiring in my house and hope that I never want to use more than 3 rooms in my entire house for computers. Or I can go to best buy pick up a few wireless cards and gateways, spend like 5 minutes configuring them, and have networking capabilities through the whole house. If you didn't notice, I don't care much about cost either, just ease of use. The ability to use my laptop anywhere in my house is also very nice.

  18. Re:A wireless network. For a dorm room. by soulsteal · · Score: 5, Funny

    Maybe he's decided to take a different course of action in the killing of superfluous sperm.

  19. Re:A wireless network. For a dorm room. by Pirogoeth · · Score: 5, Interesting

    Excessive perhaps, for just the room, but if their dorm is anything like mine was with a den down the hall or a study room in the basement or grassy areas out in front, a wireless connection like this would be pretty sweet.

    --
    Happiness is like peeing yourself. Everybody can see it but only you can feel its warmth.
  20. Hidden costs of cat5 by Anonymous Coward · · Score: 3, Funny

    What about the duct tape to hold it to the walls? Did you think about that when you came up with that outrageous $5.00 figure??

  21. Need drivers for the 802.11g by Yonder+Way · · Score: 3, Informative

    With drivers for the 802.11g adapter, more people would look at providing alternative firmwares. I've recently started working on such a project for the Dell TrueMobile 1184 because Dell actually provided source code when asked, and all the hardware support is there with open source drivers.

  22. Re:A wireless network. For a dorm room. by petree · · Score: 2

    Well first off, with WEP on, in real world conditions, you are only going to have a total of 20-25mbits or so of real bandwidth available. Don't forget, that's shared amongst all wireless users. So if I want to send a file to another wireless user (like my friend standing next to me with his powerbook) I only will get like 10mbits or so of throughput. 1.3 to 1.6MB/sec. All of a sudden it doesn't seem like that much bandwidth to me.

  23. They are still in violation by Anonymous Coward · · Score: 0

    So what? Those guys new their obligations well from the very moment they touched the GPLed code, but decided to play nookie with the community believing that they would get away with it. They violated the GPL, and no matter what time they come up with the source, they don't stop from being in violation. Being part of the community I will continue the pressure, and hopefully, by pressing charges we will manage to remove some of their capital the same way the touched our code, and fund other projects protected by the GPL.

    1. Re:They are still in violation by Anonymous Coward · · Score: 4, Funny

      Dear Link$y$:

      I am aghast and appalled at your continuing flagrant violation of the GNU Public License. Your paws are dirty with the hard work of many hundreds of thousands of kernel developers who you ripped off by $elling the kernel code back to them without supplying the full source code for your product. Through this illegal action you have raised my and The Community's ire and we will stand and fight until you fully comply with the GPL. All your source MUST be turned over to The Community at once.

      Please be aware that I am not alone in this battle. I am dogged and relentless and using the power of the Internet I will bring you into compliance with the GPL.

      Don't fuck with us, Link$y$.

      Sincerely,

      Anonymous Coward

    2. Re:They are still in violation by Anonymous Coward · · Score: 0

      The Communi[ty|sts]

  24. What the heck by Anonymous Coward · · Score: 0

    is a 'Wrtsag'?

    1. Re:What the heck by Anonymous Coward · · Score: 0

      It was the German government during the Nazi regime.

    2. Re:What the heck by MoOsEb0y · · Score: 2, Informative

      Wireless RouTer operating at 54mbps using the 802.11g protocol

    3. Re:What the heck by saden1 · · Score: 1

      It is the European version of Wanksta, which basically means wannabe gangster.

      --

      -----
      One is born into aristocracy, but mediocrity can only be achieved through hard work.
  25. just one product by frovingslosh · · Score: 1

    Good first step, but that's far from the only Linksys device running Linux. Where are the sources for the other devices?

    --
    I'm an American. I love this country and the freedoms that we used to have.
    1. Re:just one product by Daniel+Phillips · · Score: 2, Interesting

      Good first step, but that's far from the only Linksys device running Linux. Where are the sources for the other devices?

      Of course you're correct about that. But what's wrong with being nice to them just now. Let's watch them be shocked when sales of the unit tick upward, then let's ask for more, ok? :-)

      Of course, the above depends on being able to reflash the thing successfully, and as far as I can see, that's going to be a whole lot easier than the XBox was, plus more useful, including being useful to Linksys. Unlike Microsoft, they make money every time they sell one.

      --
      Have you got your LWN subscription yet?
  26. More Info by heli0 · · Score: 5, Informative

    The original post from:
    http://lkml.org/archive/2003/6/7/164/index. html
    is not up right now so here is the text.


    Andrew Miklas
    linux.kernel
    Jun 7 2003

    Hi,

    Sorry for the very lengthly posting, but I want to be as precise as possible in describing this problem.

    Awhile ago, I mentioned that the Linksys WRT54G wireless access point used several GPL projects in its firmware, but did not seem to have any of the source available, or acknowledge the use of the GPLed software. Four weeks ago, I spoke with an employee at Linksys who confirmed that the system did use Linux, and also mentioned that he would work with his management to ensure that the source was released. Unfortunately, my e-mails to this individual over the past three weeks have gone unanswered. Of course, I also tried contacting Linksys through their common public e-mail accounts (pr@linksys.com, mailroom@linksys.com) to no avail.

    However, it is hard for me to know if my contact in the company has just gone on a three week vacation (and not set an auto-responder), or has been asked to not answer anymore mail on this subject. Also, I should note that I don't own this product, so I can't determine if the source is shipped with it. However, I have gone through all the available information on the Linksys website, and can find no reference to the GPL, Linux (as it relates to this product), or the firmware source code. Also, the firmware binary (see below) is freely available from their website. There is no link from the download page to the source, or any mention of Linux or the GPL. Finally, it would be strange if the source was included in the physical package, as my contact at Linksys was initially unaware Linux was used in this product.

    The following steps can be used to determine the exact nature of the possible GPL violation.

    1. Go to the following URL:
    http://www.linksys.com/download/firmware.asp?fwid= 178

    2. Download the "firmware upgrade files":
    ftp://ftp.linksys.com/pub/network/WRT54G_ 1.02.1_US _code.bin
    (MD5SUM: b54475a81bc18462d3754f96c9c7cc0f)

    3. While it is downloading, confirm that there is nothing on the webpage to indicate that this binary contains GPLed software.

    4. Once the download is complete, copy the ontents of the file from offset 0xC0020 onward into a new file.
    dd if=WRT54G_1.02.1_US_code.bin of=test.dump skip=24577c bs=32c

    5. Notice that this file is an image of a CramFS filesystem. Mount it.

    6. Explore the filesystem. You will notice that the system appears to be based on Linux 2.4.5.
    Incidentally, there is at least one other GPLed project in the firmware:
    the BusyBox userland component: (http://www.busybox.net/)

    7. The Linux kernel (I think) is mixed up with a bunch of other stuff in: bin/boot.bin

    You might want to know why I am interested in getting the code for the kernel used in this device.

    There's been some discussion here about Linux's lack of wireless support for a few of the newer 802.11b and (nearly?) all 802.11g chips. Incidentally, Linux has excellent support for at least one manufacturer's wireless family. The following Broadcom chips all appear to be supported under Linux -- if you happen to be running Linux on a MIPS processor in a Linksys router:

    Broadcom BCM4301 Wireless 802.11b Controller
    Broadcom BCM4307 Wireless 802.11b Controller
    Broadcom BCM4309 Wireless 802.11a Controller
    Broadcom BCM4309 Wireless 802.11b Controller
    Broadcom BCM4309 Wireless 802.11 Multiband Controller
    Broadcom BCM4310 Wireless 802.11b Controller
    Broadcom BCM4306 Wireless 802.11b/g Controller
    Broadcom BCM4306 Wireless 802.11a Controller
    Broadcom BCM4306 Wireless 802.11 Multiband Controller

    This list was produced by running strings on:
    lib/modules/2.4.5/kernel/drivers/net/wl/wl.o

    I am trying to determine exactly how tightly coupled these drivers are to t

    --
    Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
    1. Re:More Info by lazyBob · · Score: 2, Informative

      As far as I know, wl.o is made by Broadcomm and is provided as part of Board Support Package (bsp). Linksys may not have its source code too.

      Even if wl.o is binary only, you may still use iwconfig/iwpriv to set wireless parameters.

      I don't agree your opinion that Broadcomm wireless module has to be covered by GPL. How can NVIDIA do binary-only driver but not Broadcomm?

    2. Re:More Info by Corydon76 · · Score: 1
      How can NVIDIA do binary-only driver but not Broadcomm?

      Consider what NVIDIA's binary-only driver is for: XFree86. See the XFree86 License. Note that it is not the GPL.

    3. Re:More Info by avdp · · Score: 1

      I believe there is a kernel module as well that's part of the Nvidia setup.

  27. I didn't think it was shared... by hackwrench · · Score: 1

    I thought that 802.11b kept each connection on completely separate frequencies.

    1. Re:I didn't think it was shared... by YOU+LIKEWISE+FAIL+IT · · Score: 2, Interesting
      Nope. 802.11b ( probably g too ) has different frequencies or channels ( different numbers thereof in different places too, e.g. 13 channels in Japan, 11? in Australia ), but this is for the separation of logical networks and/or separation of AP's on the same logical network / coverage range ( can someone confirm that last bit? ).

      Harvards wireless network usage notes includes the following:

      All devices associated with a wireless access point are in contention for part of the 11 Mbps (802.11b IETF Standard) shared bandwidth. It is for this reason that certain bandwidth intensive applications may be more appropriate for the wired network.

      It's good advice. I run mixed wireless / wireful in my house for this reason.

      YLFI

      --
      One god, one market, one truth, one consumer.
  28. I know this is a bit of a tangent, but. by Artifex · · Score: 1

    In response to another article about 802.1* a couple weeks ago, a lot of people wrote helpful comments about which cards and APs were "best" for single-, dual-, and tri-standard (a,b,g) use, many by people who had experiences with several.

    Unfortunately, I seem to have misplaced my bookmark for that article. It'd be great to get a pointer to that discussion or even spark a new discussion here, as I'm finally wanting to buy into the technology, now.

    --
    Get off my launchpad!
    1. Re:I know this is a bit of a tangent, but. by damiam · · Score: 1

      There's a little box at the bottom of this page labeled "Search". Use it.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  29. Well... by wadetemp · · Score: 5, Funny

    ... it's not just for him, it's so his neighbors can connect to his network too. Whether he knows this or not, I don't know.

  30. gpl strikes again by JDizzy · · Score: 0, Interesting

    This type of license strong-arming is the reason embeded market should choose BSD. We FreeBSD folk shun the idea of a not-so-free license like the GPL where you have free as in beer, not free as in freedom. Free, Net, and OpenBSD are free as in beer, and freedom. Linksys could have had equal if not better performance with a BSD based kernel, and there is certainly an established BSD embeded computing community. Certainly NetBSD is the most supperior embeded Open Source OS on Earth which runs on over 35 architectures.

    Well, the GPL might be good if Linksys wanted to write code that was Open source, but didn't want a competitor to takeover. Sorta like how IBM did with their JFS filesystem. SUN could take JFS, put it on Solaris, but they would have to show IBM the code that glued it together. So in this way the GPL is great for companies who want to share code, but bad for companies who want to borrow code for their own products. It appears Linksys needs to ignore a bit of the linux hype and get more practical, or continue to "cave under pressure" as the slashdot post implies.

    --
    It isn't a lie if you belive it.
    1. Re:gpl strikes again by geekoid · · Score: 4, Insightful

      BSD: free as in 'Look someone else did our work for us, and we don't have to give anything back'

      GPL: free as in 'we can use it but we have to share.'

      "...NetBSD is the most supperior embeded Open Source OS on Earth which runs on over 35 architectures."

      what does the number of architectures have to do with whether or not its good?

      Impressive, but one doesn't mean the other.

      I like BSD, but statements lke that are just irritating.

      Now if you'll excuse be, I have a bike shed to paint.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:gpl strikes again by putaro · · Score: 0, Flamebait

      It's not license strong-arming - the license is very explicit AND EVERYONE KNOWS IT. What rock would you have to have been hiding under to not know that the GPL is an evil, viral, license that forces you to make the GPL'd and modified GPL'd code available (heck, Bill Gates said so!)? Linksys had a choice - BSD is not invisible - and they chose to use the GPL'd stuff again.


      Don't blame the GPL for Linksys' failure to comply. No one held a gun to their heads and said "Use Linux". If they wanted proprietary code they could have written their own kernel or bought VxWorks (shudder) or used a BSD derivative. They didn't.

    3. Re:gpl strikes again by Platinum+Dragon · · Score: 1

      This type of license strong-arming is the reason embeded market should choose BSD.

      Well, Linksys didn't. Linksys chose to use GPL code, and now they've complied with the licence, as is expected. I'm sure Linksys would expect other companies to work within the rules of any licence on Linksys code, so it shouldn't be any different for Linksys using* GPL code. It's not strong-arming, anyway; I'm sure BSD coders would get a little ruffled if it turned out Linksys was using BSD code without proper attribution.

      * Where "using" means "modifying and distributing," which is where the GPL takes effect.

      --

      Someday, you're going to die. Get over it.
    4. Re:gpl strikes again by DASHSL0T · · Score: 4, Insightful

      Dude, license your code however you want to and let others do the same. That is freedom, not the preachy stuff you just wrote.

      Not very hard, is it?

      --
      Freedom Is Universal
      Linux-Universe
    5. Re:gpl strikes again by Daniel+Phillips · · Score: 3, Insightful

      This type of license strong-arming is the reason embeded market should choose BSD.

      Sure, Linksys would have used BSD if BSD worked as well for them as Linux does. But Linux is better, supports more hardware, and supplies more of the features they need. That's because more programmers work on Linux, and that in turn is because of the licence - we know that our contributions to the public are going to *stay* public.

      And by the way, I like BSD. I think there's some stuff in BSD that's better than Linux. I'm no fanatic, I'm just explaining the phenomenon.

      Anyway, what's the big deal for Linksys if they accidently ended up letting everybody reprogram their hardware? It just means they sell more of it and make more money. That's gotta hurt, huh?

      --
      Have you got your LWN subscription yet?
    6. Re:gpl strikes again by iabervon · · Score: 1

      But Linksys didn't have to release anything particularly proprietary, and didn't. They only had to release the code which was already public (or, rather, they had to acknowledge it), and any changes they made to that code. They wrote their own drivers and scripts, and didn't release those.

      Of course, if they'd changed any of the GPL code, they'd have to release their changes. But Linux already makes a perfectly good router without any modifications, if you provide drivers for the hardware.

    7. Re:gpl strikes again by Anonymous Coward · · Score: 0

      But Linux is better, supports more hardware, and supplies more of the features they need

      Thank you Mr. Linksys expert. Care to share what was said at the promotions meeting on Friday morning? Oh, what's that? You aren't a part of Linksys, don't know what their needs are, and are talking out your ass? I'm sorry to hear that.

    8. Re:gpl strikes again by JDizzy · · Score: 0, Troll

      Spoken like a true moron. The first thing a moron does is try to over simplify the issue to their level, as you have. Thanks =)

      --
      It isn't a lie if you belive it.
    9. Re:gpl strikes again by Namaseit · · Score: 1

      "We FreeBSD folk shun the idea of a not-so-free license like the GPL where you have free as in beer, not free as in freedom." Jeez get your facts straight before you try to insult the gnu or anything for that matter. direct quote from the gnu.org site: ``Free software'' is a matter of liberty, not price. To understand the concept, you should think of ``free'' as in ``free speech,'' not as in ``free beer." Its people like you who dont know their facts and spew bullshit that hurt the BSD and Linux community's.

      --
      75% of all statistics are made up!
    10. Re:gpl strikes again by JDizzy · · Score: 1

      Ok, I think your wrong, and here is why:

      The GPL is free as in "hey look, its free code at no cost", and nothing more. Free Speech is part of it, but there isa restriction. Yoy have to provide any modifications to the authors, as I'm surw you know.

      The BSD license has no restriction except the one about attributing the original copyright holder. It free as in "free stuff", and free as in "Freedom of use".

      The GPL is not free as in freedom, it is restricted so that you are trapped by it if you modify code and use it in a project. That is not freedom, or free speech. There is nothign free about a license that forces somebody to do something, in this case release modifications to gpl code.

      --
      It isn't a lie if you belive it.
    11. Re:gpl strikes again by merdark · · Score: 5, Insightful

      BSD: free as in 'Look someone else did our work for us, and we don't have to give anything back'

      Umm. Look, this is EXACTLY what BSD developers expect. This why it's released BSD. Shall I break out the dictionary definition of free? I'll give you a hint, it means having no restrictions. The GPL is very much a restriction. It is a very different philosophy than BSD and public domain code. It is in no way free as in the definition of the word.

      Rather, it caters to a specific ideology, namely that of the FSF. Granted, you may consider GPL to be free, and it is certainly freer than proprietary software, but it is not quite as free as BSD and public domain.

      You can be selfish and require people to share with you if you like. But, statements like yours are really irritating to those of us who want to give our code away for free.

      The guys comment was very informative given the news story. Linksys doesn't want to 'share' with you. They shouldn't have used GPL code then, but rather BSD code. Right?

      And please don't go on about how they *should* share. They are under no obligation to do so, if they did the country they operate from would certainly not be considered a free country anymore.

    12. Re:gpl strikes again by Anonymous Coward · · Score: 0

      BSD: free as in 'Look someone else did our work for us, and we don't have to give anything back'

      Umm. Look, this is EXACTLY what BSD developers expect.


      Hey, if you like working for Microsoft and Apple Corporation for no pay, be my guest...

    13. Re:gpl strikes again by Anonymous Coward · · Score: 0

      >you should think of ``free'' as in ``free speech,'' not as in ``free beer."

      GPL will become a tax much like the 'MS tax' so identified on /.

      GPL means that if you use some GPL code, 'ANY' code in your company is subject to a legal attemt to 'determine if it violates GPL' and therefore is subject to disclosure to unwanted parties (GNU/RMS).

      Been there, done that, only public domain code is actually free.

      Look up free in the dictionary and you will find that it means 'without hinderances' like GPL.

    14. Re:gpl strikes again by DASHSL0T · · Score: 1

      Yawn. I suggest you improve your reasoning skills so you don't have to resort to name calling in the future.

      Please tell the unwashed masses, especially the morons like myself, why freedom to choose the license I wish to isn't freedom.

      --
      Freedom Is Universal
      Linux-Universe
    15. Re:gpl strikes again by Anonymous Coward · · Score: 1, Insightful
      We FreeBSD folk shun the idea of a not-so-free license like the GPL where you have free as in beer, not free as in freedom.

      Freedom is created by having laws/rules. Without laws/rules there is no such thing as freedom because someone can trample another with no consequences.

      If you want to enjoy the freedoms of a society then you are expected to contribute to that society by paying taxes, upholding the laws, etc. It is dishonest to expect to enjoy freedoms of speech, religion, etc. without being required to obey the laws that create that freedom.

      The rule that creates the freedom of the GPL is that distributed binaries must be accompanied by the source.

      If you want to have the freedom to use the source in your product then you have to play by the rules. Linksys is playing by the rules because they want the freedom to use the source in their product.

      If you don't want to play by the rules then find another sandbox to play in - just don't expect the same freedom there.

    16. Re:gpl strikes again by Anonymous Coward · · Score: 0

      The GPL can co-exist with non-free software quite well thank you very much. The embedded software community agrees and so far it has done quite well.

    17. Re:gpl strikes again by YOU+LIKEWISE+FAIL+IT · · Score: 3, Insightful
      You can be selfish and require people to share with you if you like.

      I don't know if I'd consider that too selfish. Sometimes, code takes a lot of effort to design, write, test etc. And I think some return on that investment is not an unreasonable desire. Is it selfish to go to your employer at the end of the day and ask for a paycheck? A share of the value that both of you have produced together?

      Some software I release under the BSD license. I do this when I don't ever want to hear from that particular piece of software again. Some software is released under the GPL. Still other stuff goes out as Public Domain. But please don't tell me I'm selfish because I sometimes want the user community to share back with me what I've shared with them in the first place.

      I don't understand how people get into mildly flamey discussions like this. Nobody asked or forced Linksys to use Linux and other GPL'd software as the basis of their AP. They chose to do it, nodoubt for reasons of their own, and initially at least, decided not to stick to the letter with the terms of the license. They could have chosen BSD. They didn't. I'm sure they were aware of the licensing differences at the time.

      Now, hypothetically, do you think if they'd used BSD, they would have been good little angels, dilligently having their binaries displaying your copyright notice as clause two mandates? I honestly don't think so. I think they would have just appropriated the source as 'freeware', which it certainly isn't, and then we might have had the same scenes we're seeing here, but a little more low key.

      YLFI

      P.S.: I like *BSD. I like the license too. But I feel that the attitude behind the license is largely influenced by its tumultuous history intertwined with AT&T up until 1988. I think the fact that the BSD folks got to bootstrap their way up from earlier Unix sources ( and the misappropriation by AT&T of same BSD sources ) has led to a somewhat fuzzier perception of where their work ends and the work of others begins, and a less territorial mentality than the second wave GPL developers.

      These are just some thoughts. I apologise for any factual innacuracies in the above... I believe I was still playing cricket in the backyard and jumping off wharves when all this was going on.

      --
      One god, one market, one truth, one consumer.
    18. Re:gpl strikes again by tigga · · Score: 1
      But Linux is better, supports more hardware,

      Just better is very broad statement. Better for what? For use as server or workstation or for use in notebooks? I found Linux have slight edge in commercial support (like RedHat X configurator, Oracle) and lags behind in many other areas.

      On my hardware I have more support for FreeBSD for some reason.

      we know that our contributions to the public are going to *stay* public.

      That's exactly the same for BSD-licensed software. Contributions to the public remains public. What is the problem? If somebody choose to write proprietary software based on BSD - no problem - someone's code remains proprietary, BSD code still public.

    19. Re:gpl strikes again by Col+Bat+Guano · · Score: 1

      Please define your terms. For me, a piece of software that works on lots of different architectures is lilkey to have been tested in all sorts of interesting ways that hackers working on a single architecture won't have thought about. NetBSD runs on big and little endian machines. It runs on 32 and 64 bit machines. Just those two alone would affect a lot of poorly written code, and cause the O/S to be revised into robustness. It may be less efficient (if you can't take specific hardware features into account), but I'm happy to sacrifice a small amount of speed for the knowledge of running reliable software. ...now if only I -was- running NetBSD :-)

    20. Re:gpl strikes again by xchino · · Score: 1

      Name calling is the first line of defense for the mentally inferior. Of course, we have all of your other posts to verify this fact.

      --
      Everyone is entitled to their own opinion. It's just that yours is stupid.
    21. Re:gpl strikes again by Anonymous Coward · · Score: 0

      Care to share what was said at the promotions meeting on Friday morning?

      There was no promotions meeting at Linksys on Friday morning.

    22. Re:gpl strikes again by Anonymous Coward · · Score: 0

      Look up free in the dictionary and you will find that it means 'without hinderances' like GPL.

      Exactly, which is why a free society is one that simlutaneously guarantees that nobody will hinder you AND that nobody will hinder anyone from hindering anyone. In a free society everyone can be a slave trader but nobody can be made a slave.

      The only problem with unfettered freedom (and I think we both agree that it is only a very minor problem) is that it can't exist.

    23. Re:gpl strikes again by JDizzy · · Score: 1

      In your narrow view of the world, I'm sure your make perfect sense, but not here. BTW - I wouldn`t devolve this thread to be *about you*, as you suggest. You can solve for yourself any issues you have in choosing a license. This never was about you choosing a license, so bug off. In regards to my reasoning skills, I still think your a moron. =)

      --
      It isn't a lie if you belive it.
    24. Re:gpl strikes again by JDizzy · · Score: 1

      Yes, you have all my prior threads, and journals to read, have fun!

      --
      It isn't a lie if you belive it.
    25. Re:gpl strikes again by Anonymous Coward · · Score: 0

      "Freedom is created by having laws/rules."

      No, freedom is created by having a lack of laws and rules.

      "If you want to enjoy the freedoms of a society then you are expected to contribute to that society by paying taxes, upholding the laws, etc."

      Thats nice. Now tell that to the welfare mothers who leech off of our contributions.

    26. Re:gpl strikes again by martyros · · Score: 1
      Shall I break out the dictionary definition of free? I'll give you a hint, it means having no restrictions. The GPL is very much a restriction. It is a very different philosophy than BSD and public domain code. It is in no way free as in the definition of the word.

      Well, this is why RMS always says, "Think 'free' as in speech, not 'free' as in beer." It's not a perfect analogy, but it's along the right lines. When we speak of "freedom", as in "this is a free country", we definitely don't mean "no restrictions"; because that wouldn't be a free society, it would be anarchy. If you are free to live, that means I'm not free to kill you. Gangsters are not free to intimidate people, corporations are not free to lie in their annual reports.

      The restrictions in the GPL are exactly the kind of restrictions we have in a free society, and for exactly the same reasons. It's to promote the availability of source code for anyone to use, and to encourage people to write code without worrying about their work being 'stolen' by corporations.

      Now, obviously people who use the BSD license don't care about someone making money off their work without giving anything back. I don't really understand where they're coming from, but that's their choice.

      But don't diss me because I expect someone I've helped to help me back. I like to write code, I love to have other people use it and make improvements on it; but I don't want my hard work used to make money where I'm not benefitted. If there were no such thing as the GPL, I'd be less inclined to publish my code, and I'm sure many other people would be as well, and the world would be worse off.

      --

      TCP: Why the Internet is full of SYN.

    27. Re:gpl strikes again by merdark · · Score: 1

      I understand the reasons behind the GPL, but the analogy with a free country is completely wrong. This is my main gripe with the FSF dogma. Unlike in a country where anarchy is in conflict with the freedoms garunteed, public domain code is not in conflict with any freedoms. For instance, people who write software are free to keep it closed, open, or put it under a license somewhere in between.

      Public domain code can be considered free code since all of the above freedoms are preserved when the code is extended. The author of the extensions is free to do whatever they please with the code.

      The GPL on the other hand takes away my freedom of choosing a license. It is therefore not free as in a free country. It is freer than proprietary software and freeware, but it is not as free as BSD, which is not as free as public domain.

      I don't really believe that GPL code has the rights to use the "Free Software" dogma. I'd have no problem if it was advertised as "Share Software" or something similar. But the analogy with a free country is not correct.

      When I write code it's either under the BSD or a propietary license. GPL sofware is just as closed to me as free to use proprietary code. I can't use the source since I don't use the GPL.

      Most people who release BSD code have benefitted from BSD code in the past. In these cases GPL software was likely too restrictive to use. There are many exaples, grad students working on code with a different license, inexperienced developers making corporate code (remember, many of these people are just trying to live a decent life), perhaps people working on BSD based projects. Such developers feel grateful to the BSD community and often want to return the favour. We don't really care to impose our will upon others though. We give without expecting anything in return. A true gift, as everyones parents hopefully taught them.

    28. Re:gpl strikes again by martyros · · Score: 1
      I don't really believe that GPL code has the rights to use the "Free Software" dogma. I'd have no problem if it was advertised as "Share Software" or something similar. But the analogy with a free country is not correct.

      I guess when the FSF talks about "free software", they don't mean "free to you", but that the software it self is somehow "free" -- i.e., not locked up in a proprietary product. The limitations in the GPL as to what you can do to the software isn't to keep you free (you're already in a free country) but to keep the software free -- i.e., to protect it from you.

      Yeah, I think this is a bit extreme ideologically. When RMS says that it's immoral to hide code & prevent people from copying it, I think he's got his priorities a bit mixed up. There are many evil things in this world, and writing proprietary code doesn't rank that high on my list. Nonetheless, I think that making a system that keeps code "in the open", not allowing it to be folded into a proprietary product, is definitely a good thing.

      Most people who release BSD code have benefitted from BSD code in the past. In these cases GPL software was likely too restrictive to use.

      Ok, that actually makes a lot of sense. The GPL is very restrictive -- "You can use my bat, but you have to play by my rules." In that sense, they're not giving gifts, nor did they ever claim to. They wanted to make an economy where people contributed back out of their own self-interest; they didn't want to rely on people's sense of gratitude and fair-play. But I guess I can grant that gift-giving can be a good thing, and I can see why people who've been on the receiving end are disposed to give back.

      As for the inexperienced developer writing for a corporation: (unlike RMS) I have no objections to him making a decent living writing proprietary code; nor do I have any objections to him learning general coding principles from my code (tho my own code probably isn't that good to emulate). But the only reason he needs BSD code is that the company who he's writing for skimped when they hired him, or they skimped on training him; I see no reason why they should benefit from the work of an expert, even though they were unwilling to pay for an expert or train someone to become an expert; or (alternately) to make their derivative system GPL as well.

      --

      TCP: Why the Internet is full of SYN.

    29. Re:gpl strikes again by DASHSL0T · · Score: 1

      I see that you still have not worked on the reasoning skills. Or perhaps it is the reading comprehension that is causing you difficulty. In reality you opened your mouth and promptly inserted your foot and now resort to boring and childish diversionary tactics in the sad hope that will somehow distract from your untenable claims.

      So once again, explain how the freedom to choose whatever license a person wants is not freedom? Defend your position if you can.

      Oh, I forogot - you can't as there is no defense for it.

      --
      Freedom Is Universal
      Linux-Universe
    30. Re:gpl strikes again by JDizzy · · Score: 1

      I see that you still have not worked on the reasoning skills. Or perhaps it is the reading comprehension that is causing you difficulty. In reality you opened your mouth and promptly inserted your foot and now resort to boring and childish diversionary tactics in the sad hope that will somehow distract from your untenable claims.

      I already knew you were an idiot, but each time you write something you seem to remove any doubt. As I pointed out before, I do not want to devolve this thread by wasting it on you. To answer you somewhat off-thread question: it not about the *freedom* to choose a license, it's about the rights to use the licensed code, and the freedoms therein. Again, your missing the conversation about a crappy license and turning it into something about you, and your right to choose a license. I hardly think I'm creating a diversion or inserting my foot into mouth. If anything I think I just proved that you have! Please go back and re-read the thread to understand the point is about linksys would have avoided the so called "community pressure" involved in releasing the code back for the GPL'ed code they used in the 802.11 router. The point is the "GPL strikes again", and you missed it utterly, and completly. Thanks.

      --
      It isn't a lie if you belive it.
    31. Re:gpl strikes again by merdark · · Score: 1

      I guess when the FSF talks about "free software", they don't mean "free to you", but that the software it self is somehow "free" -- i.e., not locked up in a proprietary product. The limitations in the GPL as to what you can do to the software isn't to keep you free (you're already in a free country) but to keep the software free -- i.e., to protect it from you.

      Yes, I totally agree with you here. I fear that most people don't understand this though. The 'Free Software' slogan sounds good. I figure it makes people think they are gaining some sort of freedom by using it, silimar to living in a free country. But it is the *code* that is ensured this freedom. If the term 'Protected Software' or some other more descriptive term was used I don't the GPL would have nearly as many die hard supporters.

      Once you assign the freedom to an non living object, a lot of warm fuzzy feeling goes away. The moral high ground isn't so obvious anymore.

      Anyways, it's unlikely to change given how effective the 'Free Software' slogan is. That slogan is simply good marketing.

      On a side note, another reason people release BSD code is to promote quick adoption of a proposed standard. Probably the best example of this is the TCP/IP stack. The success of the BSD based TCP/IP stack is evidenced by the fact that almost all operating system's TCP/IP stacks are based off of the BSD TCP/IP stack. Even Windows uses the BSD TCP/IP stack.

      Of course, I'm not trying to suggest the GPL doesn't have it's uses. I've even released a project as GPL. But I did not do it out of kindness. Rather I did it out of greed.

  31. Thank them by geekoid · · Score: 4, Insightful

    If you use there products, shoot them a quick email to say 'thanks'.
    It really is the polite thing to do. Plus it always feels good to be appreciated, and that goes for people who run big companies.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:Thank them by Jeffrey+Baker · · Score: 2

      What the fuck for? Thanks ... for not ripping off our work? Thanks ... for actually complying with copyright laws? Thanks ... for not contributing your changes back to the projects bolstering your profit margins?

      About the only thing Linksys deserves is being closely watched for future violations (or piracy, to use an industry term).

    2. Re:Thank them by WindBourne · · Score: 1

      Not only thanx, But I told the marketing that due to gpl, I would be switching back to Linksys. I have to admit that I will test it first (Not interested in a reapeat of about 2 years ago when linksys used the atmil core - the greek division never did seem to understand admin or radio useage). But I figure that any problems will be ironed out quickly

      --
      I prefer the "u" in honour as it seems to be missing these days.
    3. Re:Thank them by ozzee · · Score: 2, Interesting
      What the fuck for? Thanks ... for not ripping off our work? Thanks ... for actually complying with copyright laws? Thanks ... for not contributing your changes back to the projects bolstering your profit margins?

      If you don't like their product then don't do it. If you do like their product more than alternatives because it is GPL'd (parts of it at least) then it makes sense to let the marketting bods know you like it this way so that they continue to do so. In fact, say that you bought their product specifically becuase it had GPL'd code and in the future you will prefer to buy GPL'd alternatives if they exist.

      On the other hand, if you want to use closed source prodcuts and don't care about the GPL buy somthing else.

      You choose.

      It's not about "thanking them", you did that when you boaught the product, it's about letting the manufacturer know what YOU want as a product.

      I'm in the market for a new wireless router, this product is definitly ahead of non-GPL'd alternatives in my purchasing decision tree.

    4. Re:Thank them by Anonymous Coward · · Score: 0

      may I have another?

      (not meant to be a troll)

    5. Re:Thank them by dereklam · · Score: 1

      This is an excellent point. Is there an email address to which we should send our thanks?

    6. Re:Thank them by praedor · · Score: 1

      I'll say "thank you" when they release a driver (binary or source) for their client cards. The AP is all but useless to the vast majority of users, I'm afraid. An AP is a very specialized piece of equipment while the client device is the meat and potatoes. What am I going to do with an AP but no decent client card to connect to it with?


      Yeah, there are a few cards out there that use a supported (or weakly/semi-supported) chipset, but they are becoming fewer and fewer. Client devices carry the same name and version but a different chipset depending on the month. You buy what you THOUGHT was going to be a prism-based card only to find it is either a poorly supported/buggy driver atmel chipset or some monstrosity that isn't supported at all (Broadcom and others). Where are the 802.11g drivers? How about drivers for even the 802.11b chips beyond prism/prism2/prism2.5? I've been burned several times in this regard and will not buy any wlan device again until I KNOW that it has a driver available or is supported by OSS drivers/developers.


      Under the circumstances, a "thank you" is premature.

      --
      In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
  32. Hella? by geekoid · · Score: 3, Funny

    You really shouldn't condem the age of 'cool beans' and still use the word 'Hella'.

    really, I've been hating the term hella since the late 80's.

    Now if you'll excuse me, I have some rad code to write that is really too hip to be square, dude.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:Hella? by Anonymous Coward · · Score: 0

      Reread the parent post and reconsider your attempt at flamage, dipshit

    2. Re:Hella? by Anonymous Coward · · Score: 0

      Can you not read, dumbass?

    3. Re:Hella? by autocracy · · Score: 1

      Writing that rad code sounds like a wicked good time...

      --
      SIG: HUP
  33. download these. mirror them by Anonymous Coward · · Score: 0

    I know this is on their website .. but one has to wonder if the higher ups know about it.

    Are people mirroring all their files?

  34. i'll GPL you by lurgyman · · Score: 5, Funny

    Slashdot... where the GNU Public License became a verb ;)

    1. Re:i'll GPL you by be-fan · · Score: 1

      Actually GPL is already a verb. "To GPL" --- To put software under the GPL.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:i'll GPL you by Anonymous Coward · · Score: 0

      Hey, don't forget that Slashdot is also where "lone gunmen" was originally verbed. :-)

    3. Re:i'll GPL you by ptr2void · · Score: 1

      It means "General Public License", not "GNU...". Why are people getting this wrong all the time? "GNU Public" - what's that? I know what the general public is, but who the hell is GNU public ;-)

    4. Re:i'll GPL you by Corydon76 · · Score: 1
      Probably because GNU is itself a recursive acronym (GNU's Not Unix), it might make sense that their license abbreviation would also itself be recursive.

      Obviously, it's not, but that might be the cause of the confusion.

    5. Re:i'll GPL you by ptr2void · · Score: 1

      The GPL public license? Another proof that recursive acronyms are stupid :-)

  35. Comment removed by account_deleted · · Score: 5, Insightful

    Comment removed based on user account deletion

  36. Still in violation by Anonymous Coward · · Score: 4, Interesting

    Vixie cron isn't a pure gpl license as you can read from their own source in the README file:

    #/* Copyright 1988,1990,1993 by Paul Vixie
    # * All rights reserved
    # *
    # * Distribute freely, except: don't remove my name from the source or
    # * documentation (don't take credit for my work), mark your changes (don't
    # * get me blamed for your possible bugs), don't alter or remove this
    # * notice. May be sold if buildable source is provided to buyer. No
    # * warrantee of any kind, express or implied, is included with this
    # * software; use at your own risk, responsibility for damages (if any) to
    # * anyone resulting from the use of this software rests entirely with the
    # * user.
    # *
    # * Send bug reports, bug fixes, enhancements, requests, flames, etc., and
    # * I'll try to keep a version up to date. I can be reached as follows:
    # * Paul Vixie uunet!decwrl!vixie!paul
    # */

    And so it looks like until linksys gives credit properly in the documentation to Paul Vixie they are still in violation of licensing agreements.

    1. Re:Still in violation by Anonymous Coward · · Score: 0

      Vixie's "license" is not very clear.

      1) What documentation is it talking about? The commented code? The product documentation?

      2) What "buildable source" should be provided? Implicitly one would expect that the source to this software be released, but there is no requirement other than "May be sold if buildable source is provided to buyer." Linksys is providing buildable source for another binary, and that means they are in compliance with the "license".

      3) No where is it implied by anyone that Vixie's name has been removed from the sources.

      4) No where is it implied that the changes made by Linksys are unmarked. A common version tracking system would keep the changes relatively clear.

      5) If Vixie had meant the product documentation that is supplied with the software, then Linksys is well within their rights as licensors of this software to write their own product documentation thereby not removing Vixie's name but rather simply not including it.

      Vixie ought to have relied on the GPL instead of this license.

    2. Re:Still in violation by Rock+Ridge · · Score: 1

      Maybe Vixie let them do what they have done. Must be a disappointment that all you get to see is what you already could have seen in your own kernel, huh? GPL will fall.

    3. Re:Still in violation by babyrat · · Score: 1

      # * Distribute freely, except: don't remove my name from the source or
      # * documentation


      Sounds like he he indicating don't remove his name from his source, or his documentation. I don't think they have his docs included in their docs.

    4. Re:Still in violation by Anonymous Coward · · Score: 0

      And what is the ntpclient? I've not downloaded the source but didn't think there was a GPL'ed NTP client.

  37. Some of the released code isn't GPL... by diamond0 · · Score: 4, Interesting
    I see vixie-cron in there, which isn't GPL. Paul Vixie, a former student at Berkeley, uses the BSD license last I knew.

    (He's better known for BIND, MAPS, PAIX, MFNX, etc.)

    --

    --
    There is no hatred more pure and true than that expressed by children.
    1. Re:Some of the released code isn't GPL... by Anonymous Coward · · Score: 0

      The version used by Linksys was GPL -- later versions were BSD licensed.

    2. Re:Some of the released code isn't GPL... by tigga · · Score: 1

      >> The version used by Linksys was GPL -- later versions were BSD licensed.

      Oh, come on, try to find GPL in here :

      #/* Copyright 1988,1990,1993 by Paul Vixie
      # * All rights reserved
      # *
      # * Distribute freely, except: don't remove my name from the source or
      # * documentation (don't take credit for my work), mark your changes (don't
      # * get me blamed for your possible bugs), don't alter or remove this
      # * notice. May be sold if buildable source is provided to buyer. No
      # * warrantee of any kind, express or implied, is included with this
      # * software; use at your own risk, responsibility for damages (if any) to
      # * anyone resulting from the use of this software rests entirely with the
      # * user.

  38. Re:Start of an era? by The+Bungi · · Score: 1

    Do us a favor and please hold your breath until that happens.

  39. Okay, so now what? by jforman · · Score: 3, Interesting

    I have this actual piece of equipment, the WRT54G. Now that I've got this code, what do I do now? I am still unable (as far as i know) to edit this code, and safely reflash my router so i can run snmp off of it, or run snort/acid/etc.

    Great, GPL the code. But now make it useful for me.

    1. Re:Okay, so now what? by Anonymous Coward · · Score: 0

      isnt taht a bit lazy? if you really feel str9ngly about it you do it... OSS development isnt about you getting sth by sitting back and doing nothing is it? thats what i do.. but i odnt wnat anything except to be able to chekc my mail.

    2. Re:Okay, so now what? by commodoresloat · · Score: 1
      snort/acid/etc.

      Sorry man that won't work; you snort coke; you have to eat acid. Or at least let it sit on your tongue a while.

    3. Re:Okay, so now what? by ffsnjb · · Score: 1

      Great, GPL the code. But now make it useful for me.

      That's your job, not theirs.

      --
      "Why do you consent to live in ignorance and fear?" - Bad Religion
    4. Re:Okay, so now what? by Anonymous Coward · · Score: 1, Informative

      You can just get the rest of the files from the cramfs image and create a new firmware file using the information at http://www.seattlewireless.net/index.cgi/WAP54G (WAP54G specific, but it's almost the same for the WRT54G).

    5. Re:Okay, so now what? by ryanr · · Score: 2, Interesting

      Wait a while, and I'll bet you'll be able to. Not from Linksys, neccessarily... but from people like me who have taken a sudden interest due to this article.

      Looks like it might be pretty straightforward to unpack the cramfs system, add a tiny .asp file to the www directory, repack, and upload. The .asp file could, say, allow shell commands. I'll let you know when my wrt54g arrives. :)

    6. Re:Okay, so now what? by warpSpeed · · Score: 1
      add a tiny .asp file to the www directory

      Wouldn't you need some sort of interpreter for asp running on the linksys box (assuming that you mean active server pages by asp)? I don't think being able to run a shell though the web server on the WAP would be that easly to do.

      I do think that unpacking the cramfs file system would be interesteing. You probably can get a real good idea of just what tricks linksys has up its sleeves for running the unit.

    7. Re:Okay, so now what? by ryanr · · Score: 1

      The unpacking has been done. It's quite easy, someone posted the instructions elsewhere in this article.

      All of the existing web scripts are .asp, but I don't think they are Active Server Pages (ala IIS.) I don't recognize the scripting language, but that's not saying much for me. It could be something well-known and I wouldn't know.

      Most (all?) of the scripts call functions and/or some kind of virtual file system built into their httpd, which I assume is proprietary? They didn't seem to give out source to that. I think it's a pretty safe bet that one could find a function through that httpd that would allow one to call busybox in shell mode.

      If that doesn't work, then I might have to figure out how to cross-compile a MIPS32 binary for Linux, and replace one of the less-used binaries with code of my choosing. I suspect I won't have to go to all that work, though...

    8. Re:Okay, so now what? by Anonymous Coward · · Score: 0
      Sorry man that won't work; you snort coke; you have to eat acid. Or at least let it sit on your tongue a while.

      Not true, check out what eMedicine has to say about LSD:
      LSD also is sold as tiny tablets (microdots), thin squares of gelatin (windowpanes), liquid, or powder. It may be insufflated, smoked, injected, used sublingually, or instilled into the conjunctiva.

      LSD can also be administered rectally; it's the most common non-oral form of acid administration in my experience.

    9. Re:Okay, so now what? by warpSpeed · · Score: 1

      Thanks for the reply.
      It sounds like it is just a matter time of before the box is hacked. It would be neat to see a linux distro for this WAP.

  40. Re:A wireless network. For a dorm room. by leshert · · Score: 2, Informative

    Perhaps he has a laptop. Wireless and laptops are good, mutually supportive technologies.

    I'm posting this from my laptop, which is only 20 feet from my AP, firewall, and DSL modem, but it's still nice not to have to run a cable across the room for someone to trip over...

  41. So when does SCO file suit? by Camel+Racer · · Score: 2, Funny

    If it contains OSS, it _must_ have been taken from SCO.... ;-) for the humor impaired

    --
    Anybody can work under ideal circumstances. -- Jeff K. (January 4, 2001)
  42. Gotta love Open Source by Dewars · · Score: 4, Funny
    From the Linksys code (udhcp/packet.c)
    const char broken_vendors[][8] = {
    "MSFT 98",
    ""
    };
    --
    --my other user id's Karma is capped
  43. Terms of Use? by femto · · Score: 2, Interesting
    Does anyone find it ironic that Linksys's GPL download page includes a link to their usual Draconian terms of use?

    On a different topic, even if Linksys hasn't provided the 'correct' source code, as suggested by some, their acknowledgement of the GPL should at least mean open slather on reverse engineering any binary which has a hint of GPL to it.

    1. Re:Terms of Use? by Anonymous Coward · · Score: 0
      Especialy interesting is the fact that the terms of use includes:
      Copyright. The Content on this Website, including, without limitations, white papers, press releases, data sheets, product descriptions, and FAQs, is the copyrighted work of Linksys and is protected under the US and International copyright laws and treaty provisions.
      Later thay point out that software may have its own terms of use, but surely the copyright of OSS compontents remains with the authors...
  44. Re:A wireless network. For a dorm room. by larkost · · Score: 1

    But then again if you were a University of Wisconsin (at Madison/Madtown) student you would be silly to put up your own access point when most of campus (should be now) set up for wireless connections, and your access point can't provide you with more bandwidth then the housing provider gives (as a former DoIT employee I have my own opinions about them...).

  45. Humor impaired? by Anonymous Coward · · Score: 0

    One of us here is humor impaired and it isn't me.

  46. Re:Linux and the GPL.. by NFNNMIDATA · · Score: 1

    All this shows is that linux is very useful...

  47. Binary modules are legal. by EmbeddedJanitor · · Score: 3, Insightful
    Assuming they are loading their drivers as modules (ie. not statically linking), then I do not beleive they are obligued to release them under GPL unless the modules were themselves based on GPL code.

    Keeping IP in binary modules is fairly straght formward way to partition IP in kernel space and is fairly common in the embedded industry.

    Now I know RMS and others frown on this, but it is not illegal.

    --
    Engineering is the art of compromise.
    1. Re:Binary modules are legal. by Anonymous Coward · · Score: 2, Interesting

      This has nothing to do with drivers. The question is, "is the source code released by linksys actually what they use on the router product?"

      Forget the drivers. Just look through the application source. Where are the linksys mods?? Are you telling me that they took the stock version of those OSS projects and just shipped them? Bullshit! There are always local mods, even trivial ones, so where are they? Take a look at what transmeta does to their open sources. They have local mods all over the place. And you're telling me that linksys shipped the sources without a single change?

    2. Re:Binary modules are legal. by Anonymous Coward · · Score: 0

      Actually, the kernel is under the GPL, which makes linking illegal (and binary-only modules are implemented by linking). Linus has said that he has no problems with binary-only modules, but he is not the only copyright-holder, others may feel different.

      Of course this doesn't matter for home users, who have no reason at all to accept the GPL (the GPL doesn't cover use, only distribution), but for a company like Linksys, distribution is important.

    3. Re:Binary modules are legal. by penguinrenegade · · Score: 1

      Where does it say in the GPL that it is illegal to link? IT DOES NOT. Please show the exact wording. See my above post.

    4. Re:Binary modules are legal. by ryanr · · Score: 1

      I think perhaps you are confusing "modifications" and "modules". They've published the GPL source they used. It appears that the kernel has been changed, according to another thread on this topic. There are a number of other programs which appear to be proprietary, such as the httpd and kernel modules (drivers) for the network interfaces.

      Until/unless someone can demonstrate that they didn't publish any GPL source modifications, or that some of the "proprietary" code contains GPL code, they don't appear to be commiting any GPL violations (anymore.)

    5. Re:Binary modules are legal. by bensonandhedges · · Score: 1

      >Until/unless someone can demonstrate that they didn't publish any GPL source modifications,

      errm read the latest posts, they have.... quite a bit of code is clearly missing

    6. Re:Binary modules are legal. by ryanr · · Score: 1

      I am. So far, I'm not seeing any evidence that they've left out code. I can't prove they didn't of course, I just don't see anything to suggest they did.

      I've replied to your post about the gcc compiler. No, they are not required to give you the gcc modifications, they didn't give you a gcc binary. What other evidence have I missed?

    7. Re:Binary modules are legal. by ryanr · · Score: 1

      OK, so here's some evidence that they might have left things out:

      http://yro.slashdot.org/comments.pl?sid=70115&cid= 6384447

  48. Re:Linux and the GPL.. by Stumbles · · Score: 0

    FACT - Todd Law is a troll, knuckle head and wouldn't know what to do with 1 rock, 1 piece of flint and some tinder.

    --
    My karma is not a Chameleon.
  49. Still in violation -- I don't think so.... by muonzoo · · Score: 3, Insightful
    In violation of what ?...
    Paul Vixie's license perhaps? ...
    I don't think so:
    # * Distribute freely, except: don't remove my name from the source or
    # * documentation [1] (don't take credit for my work), mark your changes (don't
    # * get me blamed for your possible bugs)[2], don't alter or remove this
    # * notice.[3] May be sold if buildable source is provided to buyer.[4] No
    1. Safe on this account -- you are reading the license itself, as redistributed
    2. Source appears to be unmodified -- all diffs that I can see are known patches.
    3. There it is, no problem
    4. Again, here's the source, compliant again.
    The license as stated applies to Vixie Cron, not necessarily to the aggregation of parts that is the entire product. IANAL so interpret this with council if it matters to you.
  50. Calm down, folks. by leshert · · Score: 4, Insightful

    Having followed this since the original post to the LKML, I have a slightly different viewpoint.

    Linksys got caught with their hands in the cookie jar. They probably didn't think twice about using embedded Linux; in fact, they may not have even made the decision themselves.

    When the problem was pointed out to them, they gave several weeks of no conclusive answers, and now they've put up a simple web page with some source tarballs, all or none of which may be what's actually running on the APs. You can't even FIND the page using their support search engine (a search on GPL shows no hits), and they're certainly not announcing it anywhere I've seen.

    It's the least they could do. Approximately.

    1. Re:Calm down, folks. by scottseagroves · · Score: 1
      You can't even FIND the page using their support search engine (a search on GPL shows no hits), and they're certainly not announcing it anywhere I've seen.

      If you go to linksys.com and you hit "support" you end up here. You must be talking about the search box at the bottom of that page. Look right above it. See that penguin? Looks a little like Tux, doesn't he?

    2. Re:Calm down, folks. by leshert · · Score: 2, Informative

      Indeed, it does.

      The paths I tried were:

      1. Search box from the front page of www.linksys.com.
      2. Product page for the AP in question.
      3. Downloads section of the site.

      You're right, it is obvious if you go to the support page first (I usually don't for this site, because having been there so many times, there are less clicks involved to get to drivers via the products page). But one would think that the search engine would index a superset of the support section...

      In any event, the rest of my comment stands. That , as well as the sparseness of the download page, makes be think they're doing this because they got stared down, not because they intended to do so all along. I've seen hardware companies that buy into open source/Free software, and this isn't one of them.

    3. Re:Calm down, folks. by dachshund · · Score: 1
      It's the least they could do. Approximately.

      Actually, the GPL only obligates Linksys to mail out a copy of the code on written request. Technically, that's the least they could have done.

      I agree that we shouldn't be lauding them for merely deciding to obey the law. But I'm willing to give them the benefit of the doubt this time, and assume that it was an oversight on their part. A big, stinky oversight.

  51. Re:Linux and the GPL.. by Anonymous Coward · · Score: 0

    FACT: You have no sense of humour. FACT: a sense of humour is indicative of intelligence. FACT: You will think "humour" is spelled wrong because you are completely ignorant of the fact that "American English" is used only by one country on the planet.

  52. Thanks for your ad...I mean advice by Anonymous Coward · · Score: 0

    God I hate it when people make links on Slashdot to Amazon, and have their affiliate ID embedded in the URL, without bothering to mention it. And I doubly hate it when such "informative" posts are modded up rather than down.

  53. GPL is a subset of BSD by shepd · · Score: 1

    I think I've said this before, but if you license under the BSD license, you must like all licenses, as any license (including the GPL) can be applied to your project at any point, and any further development on that new version will be out of your hands, as far as relicensing goes.

    How can you say you shun the GPL when, not so indirectly, you support it? It simply doesn't make any sense.

    --
    If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    1. Re:GPL is a subset of BSD by JDizzy · · Score: 1

      That simply doesn't compute. Yes, the GPL can asymilate any code that is more free than itself. In regards to BSD developers supporting the gpl, even by theory of indirect contribution by simply existing, is utter naivety. Thats like saying I support getting the flu because I'm human and am therfor suseptible to viral disease. And in the thought experiment you suggest, then Linksys (for example) would have two parallel options to choose ofthe same thing, and you you belive they would take the not so free version for their modification? I hardly think they would in that situation.

      --
      It isn't a lie if you belive it.
    2. Re:GPL is a subset of BSD by JunkMale · · Score: 1

      You cannot change the license of a project without the consent of all contributors. To claim that you can take, for example, FreeBSD and apply the GPL is incorrect.

      You can however, take code from a BSD-licensed project and incorporate it into a GPL'd project, provided you observe all BSD-license restrictions.

    3. Re:GPL is a subset of BSD by Anonymous Coward · · Score: 0

      No it isn't. Its more like saying you support getting the flu because you support getting sick. But:

      BSD developers support having their code licensed as GPL because their license allows that (and more). It doesn't mean they support the restrictions which the GPL imposes though.

  54. Linksys has crapy firmware by fldvm · · Score: 1

    I just wish they would opensource the firmware for their BEFVP41 I have two of em for a home to office vpn but the vpn tunnels drops after a few days of being up. This has been a known problem for a while but they haven't released any updates since Nov 21 2002. http://www.dslreports.com/forum/remark,5873922~roo t=equip,16~mode=flat

    1. Re:Linksys has crapy firmware by fdragon · · Score: 1

      They released a new update January this year. What I noticed as weird about it is that it is only on the BEFVP41 that you buy new, you cannot download it.

      I noticed this when i just purchased a new one of these to setup a VPN between me and my friends place.

      I don't know if this is an intended feature or not but with the reconnect VPN on demand nature of the connections I do not mind that it will drop it. There is of course the advanced property to put an anti idle into the data streams as well.

      No I don't work for LinkSys, just got too familiar with their products of late...

      --
      The program isn't debugged until the last user is dead.
  55. Re:Linux and the GPL.. by Anonymous Coward · · Score: 0

    Where's your proof

  56. Wireless is subject to FCC regulations by yerricde · · Score: 5, Insightful

    What I want, and what I know many other people want, is an 802.11g driver.

    Many makers of 802.11g cards cannot lawfully provide such a driver under various radio frequency emission regulations. Because it's more expensive to build interlocks that prevent over-powered transmissions in hardware than in software, many cards implement the interlocks only in the driver. This makes it a bit harder to justify getting FCC approval for a driver for each platform.

    Linksys has one. They choose not to release it?

    Is it Linksys's choice, or is the Federal Communications Commission's choice to delay approval?

    --
    Will I retire or break 10K?
    1. Re:Wireless is subject to FCC regulations by benjamindees · · Score: 4, Informative

      Linksys has one. They choose not to release it?

      Is it Linksys's choice, or is the Federal Communications Commission's choice to delay approval?


      Actually, it's probably neither. The driver is from Broadcom. It's mentioned in some of their online documentation. They probably haven't and won't release it, even as binary-only, because they'd rather license it to Linksys for an additional fee. I'm assuming a binary-only driver wouldn't incur the FCC regulations you're referring to.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    2. Re:Wireless is subject to FCC regulations by tigga · · Score: 5, Informative

      There are drivers for FreeBSD (ath) and Linux http://sourceforge.net/projects/madwifi
      Supported cards:
      Card Chip Bus
      D-Link DWL-AB650 AR5211 Cardbus
      D-Link DWL-AG520 AR5212 PCI
      D-Link DWL-AG650 AR5212 Cardbus
      Linksys WMP55AG AR5212 Cardbus
      Linksys WPC51AB AR5211 Cardbus
      Linksys WPC55AG AR5212 PCI
      Netgear WAB501 AR5211 Cardbus
      Netgear WAG511 AR5212 Cardbus

      Those drivers are beta quality but work.

      There is object file which hides radio interface.
      AFAIK everything else is open.

    3. Re:Wireless is subject to FCC regulations by Florian+Weimer · · Score: 3, Insightful

      Many makers of 802.11g cards cannot lawfully provide such a driver under various radio frequency emission regulations.

      Irrelevant. The ISDN subsystem of Linux has exactly the same problem (well, even worse, regulation is stricter in the old telco world), and there is source code. Some versions have even been certified, and it's legal to run them on public networks.

    4. Re:Wireless is subject to FCC regulations by eggboard · · Score: 1

      Actually, if Broadcom's 802.11g chips use software-defined radio (SDR), which I believe but am not sure that they do, the FCC won't allow them to offer open access to the hardware because it can then be "redefined" to use spectrum that's not allowed.

      This is tricky: you can't say, who cares?, because Broadcom has to as they're the one that will be fined and have their equipment recalled.

      You can read about Sam Leffler's work with Atheros that allowed him to create a proprietary hardware abstraction layer and then an API to it. This let Atheros provide (indirectly) Linux, FreeBSD, etc., support without violating FCC rules. It gave them an arm's length distance, while licensing just to Sam the hardware details. The HAL has to stay a black box, Sam said at a BAWUG (Bay Area Wireless User's Group meeting) in April.

      Sam's drivers are now part of the FreeBSD tree. So someone needs to be able to cultivate a relationship with Broadcom or convince Broadcom to write a HAL themselves.

      --
      Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others
  57. Re:Linux and the GPL.. by Anonymous Coward · · Score: 1, Funny

    Who needs proof?

    If the president of the united states of america doesnt need proof to invade and conquer a sovereign nation than why would someone need proof to show that linux is a tool of communists and other scary evil doers?

  58. don't bother by 73939133 · · Score: 1

    It's good to see that Linksys is complying with the GPL. It's unfortunate that they are not making their platform more compelling by releasing a complete source tree.

    In the end, Linksys APs are just not very good. I have had two, and both of them have had serious bugs. They are now stuck in a closet. Furthermore, their functionality was pretty limited as well.

    So, if you want something hackable or powerful, don't bother with the Linksys APs. You are better off with a Mini-ITX board running Linux or BSD and some dumb wireless hardware (USB, wireless bridge, etc.). It's a little more expensive up-front, but much higher quality and much more flexible and functional.

  59. Re:Linux and the GPL.. by Anonymous Coward · · Score: 0

    Proof is just something evil doers use to look innocent.

    Like that terrorist linux torvilds i bet if you try to arrest him for terrorism he would ask for proof!

    Luckily with the USA patriot act you just have to be a muslim, spooky or just different to have your citizenship revoked and be sent to face a military tribunal in a prison camp.

    GOD BLESS USA!!!!

  60. Cisco... by LucidityZero · · Score: 1, Offtopic

    Why has no one brought up that they are now owned by Cisco? Cisco is normally regarded as a fair and tolerant company, overall. I mean... I know they just purchase anyone that might be competition, but... I've always held Cisco in pretty good light...

    --
    Sig.i>
    1. Re:Cisco... by dago · · Score: 1

      just my cisco-not-sponsored comment : they do not purchase anyone that might be competition (otherwise alcatel, juniper may have been bought, for example), but they purchase when they have want to expand into one domain : it cost less to them to buy some company than to build up entire knowledge.

      And, contrary to some convicted monopolies, they are openly listing all their acquisitions on a web page.

      --
      #include "coucou.h"
  61. Why reply to your own post as AC? Dipshiat by Anonymous Coward · · Score: 0

    moron

  62. Hey! by multipartmixed · · Score: 1

    That's GNU/Public to you!

    --

    Do daemons dream of electric sleep()?
  63. Not only Linksys... by lobsterturd · · Score: 2, Informative

    I know that many more networking equipment manufacturers use GPL'd code in their products. Buffalo's wireless broadband routers use almost the same code as the WRT54G, and earlier Linksys routers used Linux as well.

  64. K...rad by paulthomas · · Score: 1

    Well at least it wasn't k-rad, my hax0r friend.

    1. Re:K...rad by Anonymous Coward · · Score: 0

      If you didn't just mention k-rad, I probably would've forgotten it forever. Damn you! Now my brain has one less address space available to store other useless crap I should have forgotten by now.

  65. Re:A wireless network. For a dorm room. by Anonymous Coward · · Score: 1, Interesting

    I don't know about you, but I don't really have too many 1 gig files I need to transfer through thin air in under a minute. That kind of bandwidth is still suitable for streaming video, and just try and tell me you don't think it'd be cool to ssh from your 802.11g enabled pda into the box next to your tv to stream a movie from the box in your basement. Fine, not too many people actually have this setup, but as I'm completing my media PC and have a couple p2's dying for a job, it seems like a good idea to me....besides you insensitive clod, broadband isn't even available in my area, you're so ungrateful to scoff at 1.3MB/s transfer speeds...I shall shit on your grave!

  66. All this is great, but one complaint by little+alfalfa · · Score: 1

    Sure it's great that they're doing this for a nice 54mbps wireless router, but what happened to the WMP11 v2.7 wireless card? I thought they were going to release a gpl gnu/linux driver for the broadcom chipset version. Here I am, stuck with this stupid card that won't work under my favorite o/s. What's a nerd to do?

  67. Sweet! by appleLaserWriter · · Score: 2, Funny

    Now SCO can sue Linksys too!

  68. It's a start... by iwrasahp · · Score: 1

    So Linksys is just now beginning to use GPL'd code? More likely, they have been using it for a while in their product line and haven't complied with their obligation to the (L)GPL. Does anyone have information as to when they began or what product first used GPL'd code? I'm interested as I have quite a bit of Linksys gear and would like to squeeze more life and utility out of it...

  69. How naive by SuperBanana · · Score: 1

    It's really great to see a company that saw it had made a mistake, corrected it and moved on. My only wish is that more companies would take that attitude.

    How cheerfully naive. Let me play devil's advocate, for you:

    "It's not very nice that companies are violating the GPL freely, and only after intense pressure and negative PR does one of them actually follow the terms of the license. My only wish is that people would wake up to how many other companies are doing exactly what Linksys did, or even worse, simply cutting and pasting sections of code".

    Sorry, but you'd have to live in a fucking cave to not know what the GPL is by now if you're in the computer industry, especially a programmer. These guys knowingly violated the license and figured no one would ever catch them.

    1. Re:How naive by Anonymous Coward · · Score: 0

      Or you could live In taiwan or mainland china. Or you could be a marketing Dweeb or any number of other things. Is it the fact that this was resolved amicably upsetting you or is it something deeper ?

  70. Obviously by appleLaserWriter · · Score: 1

    Well, of all the superior operating systems that run on more than 35 architectures, and you can bet there are a lot of them, NetBSD is the most superior. This is handy to remember in case your review goals include "developing superior embedded systems." When you are in a team of 85 engineers working to develop superior products, you need something to make your work stand out. You need the most superior embedded Open Source OS (on Earth). Don't forget!

  71. What linksys didnt release is... by jonwil · · Score: 5, Interesting

    The code to whatever custom build of GCC was used to compile the things in the first place...

    1. Re:What linksys didnt release is... by beezly · · Score: 2, Interesting

      That's probably because they don't have to. GCC isn't included with the AP.

    2. Re:What linksys didnt release is... by Anonymous Coward · · Score: 0

      No, but they are necessary to build the system. The GPL includes stuff necessary to build the system, with exceptions for stuff like compilers *that come with the system*

      The idea is to make it impossible to render the GPL useless by releasing the derived product in some in-house language, that you can only compile if you pay for the compiler.

    3. Re:What linksys didnt release is... by ryanr · · Score: 2, Insightful

      Most of the binaries say:

      GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications

      I don't follow GCC versions that closely. Does that indicate a customized (non-public) version of GCC?

      Any reason to think that a current GCC 3.xx won't work with this target hardware?

    4. Re:What linksys didnt release is... by chrysalis · · Score: 1

      > That's probably because they don't have to. GCC isn't included with the AP.

      This brings an interesting question. Should free software be redistributed with compilers that were used to generate binary packages?

      If not, it would be possible to distribute source code that no one could compile. But this would still be opensource software. There's even no need to write a new compiler to do this. Encrypt the source code with GPG, say that your compiler is actually a simple wrapper that decrypts the source code before calling gcc et voila. You can distribute the encrypted source code that no one would be able to use. But this will be the real source code, so the project will be opensource.

      But this is the chicken and egg problem. If opensource software should distribute the compiler that was used to generate binary packages, the compiler itself should be distributed with tools that were used to build it.

      --
      {{.sig}}
    5. Re:What linksys didnt release is... by QuMa · · Score: 2, Informative

      You have to distribute the preferred form for editing, at least for the GPL. So encrypted source wouldn't be allowed. If you wanted to design a new language, convert the GPLed code you want to use to that language and write a compiler for that language which you don't distribute, you could do that however.

    6. Re:What linksys didnt release is... by Anonymous Coward · · Score: 0

      bcm probably indicates Broadcom, the maker of the chipset used in the Linksys.

  72. Hey there still viloating the gpl! by pigscanfly.ca · · Score: 0, Redundant

    Now firstly INAL ; but from my understanding there distributing a complete binary (the rom upgrade) in binary form of a compiliation of GPL and LGP etc. works . The problem is that they havent released all of the code contained within this one honkey binary program/file ; I want the drivers!
    (Note : If I'm wron please let me know).

    1. Re:Hey there still viloating the gpl! by spitzak · · Score: 1

      You are wrong. Linux explicitly allows closed-source programs to be run on it, and closed source "modules" to be added to it.

    2. Re:Hey there still viloating the gpl! by Anonymous Coward · · Score: 0

      maybe the reason they didnt include a GPL was to prove that no code was taken from linux (im probably wrong)

      but has anyone actually looked at the source code?

    3. Re:Hey there still viloating the gpl! by Anonymous Coward · · Score: 0
      You are wrong.

      Yes you are.

      Closed source programs aren't an issue, since they aren't a derivative of the kernel. The license for linux only explains this, it dosen't explicitly allow it.

      Closed source modules aren't allowed. However, as long as they only use the standard kernel API for modules, they aren't considered derivatives of the kernel. The license for linux only explains this, it dosen't explicitly allow it.

    4. Re:Hey there still viloating the gpl! by Anonymous Coward · · Score: 0

      No, Linux is licensed under the standard GPL v2. There are no special exceptions. Linus interprets the GPL as allowing binary-only kernel modules (for apparantly no reason other than he wishes it to be so). Not all kernel developers agree with him, and the legality of distributing binary-only kernel modules is a matter of dispute.

  73. The ransom model by yerricde · · Score: 1

    They probably haven't and won't release it, even as binary-only, because they'd rather license it to Linksys for an additional fee.

    Would it be possible for the public to pony up such a fee through PayPal? Is the domain 11g-ransom.org available?

    --
    Will I retire or break 10K?
    1. Re:The ransom model by Ian+Jefferies · · Score: 1
      They probably haven't and won't release it, even as binary-only, because they'd rather license it to Linksys for an additional fee.


      Would it be possible for the public to pony up such a fee through PayPal? Is the domain 11g-ransom.org available?

      The company that Linksys licenced the drivers would not be under any obligation to enter into a licensing arrangement. Even if they did you can be sure that source code access would be locked under an NDA, and you wouldn't be allowed to release the source under a different license.

      Ian.
      --
      A physicist is an atom's way of thinking about atoms
  74. Re:A wireless network. For a dorm room. by Gumber · · Score: 2, Insightful

    Why should there be any relationship between the size of his dormroom and the throughput of his wireless net?

    I often use my wireless connection sitting just a few yards from my access point. Sure beats dealing with a cable.

  75. My take on the GPL by Vicegrip · · Score: 1

    BSD: groovy, take it man, go ahead, make money from my work and close it up.

    GPL: want it for Free? Then make yours Free too. Want to keep it closed and sell your derivative? Pay me money and I'll give you another license.

    Free in the BSD sense is very noble and the BSDs have given so much. For me though, given the way everything today is becoming "intellectual property, DMCAed etc..", I just can't digest the idea of somebody making my work THEIR property (closed and commercial) and never seeing a penny of reward.

    --
    Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
  76. Re:Why reply to your own post as AC? Dipshiat by Dewars · · Score: 1

    Hmm... That wasn't me that replied. I sort of agree though. I didn't make that code up. Download the code, look at packet.c. If that code is trolling then blame Linksys, not me.

    --
    --my other user id's Karma is capped
  77. Linksys - a part of Cisco by (IQ)_Morten · · Score: 1

    Have a look at the changelog for the firmware - it says "Linksys, A division of Cisco Systems, Inc."

    --
    At the end of the world, There will be no more dolphins
  78. Re:GPL paradox. by Anonymous Coward · · Score: 0

    No, they would be sued for copyright violation. Copyright law covers all software, so seing Linksys (or someone else) sued for copyright violation should not make anyone postpone their implementation of Linux. What else would they choose? Windows? People violating MS copyrights are much more likely to be sued for copyright violation.

  79. Nonesense - you deny our freedom by Anonymous Coward · · Score: 0
    A people are most free only when their essential freedoms are realized. The freedoms spoken of in the GPL are essential freedom. These are freedoms due to us in virtue of being human beings, members of the universal social and moral community.

    You wish to deny us our essential freedoms. You have bought into the lie propagated by the present order of this world.

    "It is in no way free as in the definition of the word."

    The GPL is a "freedom promoting" license.

    No one is suggesting that you, an individual recipient of the code, can not in the present legal system use BSD code with fewer restrictions than GPL code. The question is whether you ought to be able to do this.

    First though, it seems important to note that despite RMS being exceedingly vigilant in distinguishing between "free as in beer" and "free as in freedom promoting", you simply are not willing to listen.

    The GPL is more "free as in freedom promoting" than is the BSD.

    When you license code under the GPL, if a private individual or corporation modifies that code and wishes to redistribute it, then the terms of the GPL specify that this private individual or corporation must distribute these modifications under the terms of the GPL.

    This is why the GPL is "free as in freedom promoting". When this private individual or company distributes modified GPL code, the GPL ensures that this additional (hopefully) quality software application or library will be available first to the immediate recipient, and indirectly to all of society, and available in a mode which is equally freedom promoting.

    In the case of the BSD, such a private individual or company need not promote these freedoms, because the BSD is not inherently a freedom promoting license.

    Second, that you are legally permitted to distribute code under the BSD license speaks to the immorality of the present system. The GPL is a hack, necessary until the present immoral system -- the present order -- has passed away, and a new order more noble and free has risen in its place..

    The FSF and its supporters maintain that it is the right -- an ethical right -- of the recipient of a software application or library to have realized by the distributor these essential freedoms spoken of in the GPL.

    Copyright law as it presently applies to the distribution and use of software, is immoral so far as it does not realize and promote these essential freedoms.

    "They are under no obligation to do so, if they did the country they operate from would certainly not be considered a free country anymore."

    Oh, do spare us your "patriotic" ranting!

    Again, and I will say this as many times as is needed to get it through your thick skull: a people are most free only when their essential freedoms are realized. The freedoms spoken of in the GPL are essential freedom. These are freedoms due to us in virtue of being human beings, members of the universal social and moral community.

    In closing, an excerpt from "Why Copyleft?":
    "In one such argument, a person stated that his use of one of the BSD licenses was an "act of humility": "I ask nothing of those who use my code, except to credit me." It is rather a stretch to describe a legal demand for credit as "humility", but there is a deeper point to be considered here.

    Humility is abnegating your own self interest, but you and the one who uses your code are not the only ones affected by your choice of which free software license to use for your code. Someone who uses your code in a non-free program is trying to deny freedom to others, and if you let him do it, you're failing to defend their freedom. When it comes to defending the freedom of others, to lie down and do nothing is an act of weakness, not humility. (emphasis mine)"
  80. Re:Why reply to your own post as AC? Dipshiat by DeathPenguin · · Score: 1

    I rated it as flamebait or offtopic or whatever since the changelog states: Force broadcast to broken clients that request unicast (ie, MSFT 98)

    So yeah, there's another problem with networking in Windows '98. I think the person who started the thread was taking it out of context intentionally and making it look worse than it really is to help himself in taking a cheap shot at Microsoft.

  81. Read "Why Copyleft?" again by Anonymous Coward · · Score: 0
    Haven't read it recently? Have another look. You are forgetting what this is about. You are buying into the lie of the present order.
    " Humility is abnegating your own self interest, but you and the one who uses your code are not the only ones affected by your choice of which free software license to use for your code. Someone who uses your code in a non-free program is trying to deny freedom to others, and if you let him do it, you're failing to defend their freedom. When it comes to defending the freedom of others, to lie down and do nothing is an act of weakness, not humility."

    "Why Copyleft?"

    Read it in its entirety again, brother.

    Read it often and do not forget it.

    Fight for our freedoms, the freedoms of the oppressed and down-trodden.
  82. Caved in due to "Community Pressure" by svachi · · Score: 3, Interesting
    Maybe it's just me, but after reading the term, I visioned a "community" mob treatening to burn Linksys's complex to the ground, Linksys gave in, the mob get what they want, and Linksys swear they won't do anything with the community again.

    IMHO, Linksys just honors the license of the software they used. Maybe they just strayed a bit, but it's not like they are actively trying to violate it. Why don't we put a better positive word to the situation? It will make the "community" sound like a more pleasant entity to interact with when we don't go pressuring people for what we want.

    --
    --- (The signature is intentionally left blank)
  83. Broadcom violates the GPL, not LinkSys? by Anonymous Coward · · Score: 2, Interesting

    Broadcom distributes/sells the GPL'd code including a modified GCC compiler ("GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications."), allowing the OEMs to modify the sources and recompile. They didn't release the sources of the GCC compiler, which is required IMHO. The code released by LinkSys cannot be modified without this compiler because the Broadcom CPU has extra instructions in addition to the MIPS3000 instruction set.
    Using GPL'd software to make a profit and not releasing (available) drivers to support their hardware on the same GPL'd software does also not feel right to me. At least morally.

    1. Re:Broadcom violates the GPL, not LinkSys? by ryanr · · Score: 1

      Broadcom distributes/sells the GPL'd code including a modified GCC compiler ("GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications."), allowing the OEMs to modify the sources and recompile.

      Do you know for sure that they have distributed the compiler, and not just pre-compiled binaries? If they have distributed their modified gcc, then we would need to find out to whom, and see if they will request a copy of the source, and give it to us.

    2. Re:Broadcom violates the GPL, not LinkSys? by bensonandhedges · · Score: 1

      i guess we would need to lean on one of the vendors or buys the BCM94710 evaluation kit or write an open letter to Broadcom denying that they do (lawyers don't like setting themselves us to be caught)

      I would doubt if Broadcom could NOT distribute the compiler given the midifications that it is clear that the vendors are making

      i.e. string run over the belkin and linksys kernels highlight that they are including modified header files from local directories e.g. /home/hyin/cvs/BELKIN/ASKEY_31190/src/linux/linux/ include/linux/skbuff.h ghow could this be there if Belkin did not compile ther kernel themselves , how could the compile the kernel on this modified MIPS32 without the modified compiler

      Also the vendors seem to be including their own open choice of packages/utilities this agin would require the modified compiler.

    3. Re:Broadcom violates the GPL, not LinkSys? by Anonymous Coward · · Score: 0

      If you check the file /sbin/rc, you will find both strings "GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications" and "Linksys WRT54G" which proves LinkSys used the compiler to build their version op the /sbin/rc binary.
      I downloaded version 1.30: WRT54G_1.30.1_US_code.bin.

    4. Re:Broadcom violates the GPL, not LinkSys? by ryanr · · Score: 1

      I've combed through Broadcom's website, but pretty much everything eventually leads to "call us for product info". They make reference to a software kit for their reference design, but it doesn't relly say exactly what comes with it (the compiler, or not.)

      The files from Linksys give every appearance of just being the ones that Broadcom compiled and gave out. So, I can't determine for sure if they give it out or not.

      I had already requested processor specs from Broadcom yesterday, we'll see if I get anything. Maybe they'll sell me a reference design and software toolkit?

    5. Re:Broadcom violates the GPL, not LinkSys? by Anonymous Coward · · Score: 0

      More proof that Linksys used the modified GCC compiler? /usr/sbin/httpd:
      "LINKSYS.Vendor:" "Linksys WRT54G" "W54G"
      "GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications." /usr/sbin/upnp:
      "Linksys WRT54G" "http://www.linksys.com/" "Linksys Inc" "Linksys WRT54G"
      "GCC: (GNU) 3.0 20010422 (prerelease) with bcm4710a0 modifications"

      [version: WRT54G_1.30.1_US_code.bin]

  84. You deny us our freedoms by Anonymous Coward · · Score: 0
    Brother, you forget what the revolution is about.

    It is ousting the existing immoral order of this world which denies us our essential freedoms, which oppresses and ensalves us, and which would use us to propagate its very lie were we not strong.

    Have you read, "Why Copyleft?" lately? Have you read it today?

    Recall this excerpt to strengthen your mind and your body, brother:
    " Humility is abnegating your own self interest, but you and the one who uses your code are not the only ones affected by your choice of which free software license to use for your code. Someone who uses your code in a non-free program is trying to deny freedom to others, and if you let him do it, you're failing to defend their freedom. When it comes to defending the freedom of others, to lie down and do nothing is an act of weakness, not humility."


    "Why Copyleft?"

    Read it again in its entirety.

    Read it often and do not forget its teachings.

    Be strong and fight the good fight. We will overcome. We will overcome.
  85. You have no idea, do you? by Anonymous Coward · · Score: 0
    How many damned times must this be stated again, and again, and again? You have not the slightest idea the lies and slander you speak. You are thoroughly unable to think a thought independent of the present immoral order. You are a puppet, and it and its guardians are your masters.

    READ, for the love of GOD, READ: "Why Copyleft?".

    If you read anything, read this excerpt:
    "In one such argument, a person stated that his use of one of the BSD licenses was an "act of humility": "I ask nothing of those who use my code, except to credit me." It is rather a stretch to describe a legal demand for credit as "humility", but there is a deeper point to be considered here.

    Humility is abnegating your own self interest, but you and the one who uses your code are not the only ones affected by your choice of which free software license to use for your code. Someone who uses your code in a non-free program is trying to deny freedom to others, and if you let him do it, you're failing to defend their freedom. When it comes to defending the freedom of others, to lie down and do nothing is an act of weakness, not humility."

    Read it often, and understand it.

    Read it now. Read it tonight. Read it tomorrow. Read it every day and recite it with every breath until you understand it, and understand the battle we fight.

    Understand what this is about, and why it is so very dear.

    Understand that it is your RIGHT to have the essential freedoms spoken of in the GPL, realized.

    The present system of copyright law is immoral; it denies us our essential freedoms, it decieves us into deny those freedoms to others, it binds us, it gags us.

    We are being used by the powerful elite, and you, you who do not understand without thought prostitute yourself to them for their own vile purposes.

    Open your eyes, man! Look at what is happening, and fight, for the love of God, FIGHT!
  86. Find a security crack... by Ian+Jefferies · · Score: 2, Funny

    Can the OSS community now modify the firmware and make custom things for it?

    Perhaps we can find a security crack and get Linux to run on it.

    Uh... cancel that.

    --
    A physicist is an atom's way of thinking about atoms
  87. Actual text of GPL by penguinrenegade · · Score: 3, Interesting

    This is how you can get away with releasing only the ORIGINAL code, and not the Linksys mods.

    Quote:
    The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language.

    Think about it. They distributed the source for the "Program" as outlined above. "A work based on the Program" can refer to either the Program (the original) or the "work based on the program" - that is, the derivative. So, if you take it to always mean "The Program" or the ORIGINAL program - then you only must distribute the ORIGINAL PROGRAM and not the mods! Perfectly within the GPL.

    I'll get modded down on this, but HONESTLY the GPL says this. It does not say that "The Program" means BOTH, but EITHER.

    The GPL doesn't say you have to release your mods, but only a list of the changes and what dates. Have you actually read the GPL?

    The other problem with the GPL is that there is conjecture and opinion throughout, not fact, as there must be in an Agreement. IANAL but I worked in the world of Contracting (as in Construction) and you must specify everything, not give opinion.

    "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."

    This is an OPINION that "the best way to achieve this." Sometimes making it of the greatest possible use to the public is to never use it. For instance, the software that drives nuclear missles. This is a deterrent. The best way to use this technology MIGHT be not to use it, not make it software which everyone can redistribute.

    The first time the GPL gets tried in court it will get thrown out because it's full of opinion, and holes like I just pointed out. And remember, I'm FOR Open Source. I just think that Richard Stallman tried to force his opinions on everyone else's work. "Free" my butt. (And I know the difference between free as in beer, etc.) Here's a quote from the FSF website:

    "The $5000 Deluxe Distribution includes all GNU software compiled for your choice of computing platform (micro-chip and operating system). Please contact the FSF Office if you are interested."

    "Free" my butt. $5000 US is a LOT of money for a program, period, ESPECIALLY for one user.

    Go Linksys. MAKE money. PROVIDE a valuable service!

    1. Re:Actual text of GPL by Patrick · · Score: 1
      It does not say that "The Program" means BOTH, but EITHER.

      That's a strange reading. What the GPL actually means when it says "either the Program or any derivative work under copyright law" is that either one you choose to distribute -- the original or the derivative -- is still "the Program" under the license. It means you can distribute EITHER, and it will still have to be GPL.

      Have you actually read the GPL?

      Yes. Have you actually understood the GPL?

      IANAL but I [snip]

      But Eben Moglen, who wrote the GPL, is. This is the sort of language he's likely to get right, whether or not you personally understand it the same way a court would.

      "Free" my butt. $5000 US is a LOT of money for a program, period, ESPECIALLY for one user.

      You're wandering pretty far off-topic there. Just feel like ranting about free software today, or what? That $5000 is essentially a consulting fee. Once you have that custom CD, made just for your sorry butt, you can make as many copies or modifications as you please. Free software is about freedom -- to use, to copy, and to modify -- and not always about freeloading.

      Of course, the source is, as always, on gnu.org. For free in both senses of the word.

    2. Re:Actual text of GPL by booch · · Score: 1
      The GPL doesn't say you have to release your mods, but only a list of the changes and what dates. Have you actually read the GPL?

      I've read and analyzed the GPL license many times. It's pretty clear (in spirit and literally) in stating that you must release any modifications if you distribute modified binaries.

      a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications

      Your interpretation of this to not mean both is pretty shaky. Try replacing the word "either" with the word "both" in the text. That'd mean that a derived work is 2 separate things. Besides, Section 2 of the GPL is effective even without the definition of "work based on the Program":

      You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: [...] b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
      The other problem with the GPL is that there is conjecture and opinion throughout, not fact, as there must be in an Agreement.

      The opinion portions of the license are only in the "Preamble" and the "How To Apply These Terms" sections. The "Terms and Conditions" section is clearly marked as the only part constituting the actual agreement. Also, it says "If you develop a new program, and you want it to be of the greatest possible use to the public".

      The first time the GPL gets tried in court it will get thrown out because it's full of opinion [...] Stallman tried to force his opinions on everyone else's work.

      But if the GPL gets thrown out, then you have no right to distribute or modify the programs under the GPL. (Because default copyright law does not allow those.) So I'm not sure it can even be thrown out. If it does, what would happen? Would the judge say that distribution of all the GPL code out there is now illegal? Or would he say that it's all in the Public Domain? Neither choice would make sense.

      The GPL is actually a pretty straight-forward contract, compared to other software licenses such as Microsoft EULAs. And it doesn't take away any existing rights you have -- it just specifies the conditions you must follow to gain additional rights. And it's hard to make the case that Stallman is trying to force his opinions on anyone; he doesn't make anyone apply the GPL to their code. If you want to use the GPL, or derive your code from existing GPLed code, that's fine; if you don't, that's fine too -- choose your own license for your own code. It's people telling me that I shouldn't use the GPL for my own code that are trying to force their opinions. (And trying to say that code derived from GPLed code doesn't give me a choice is a red herring. Try deriving code from Microsoft copyrighted code and see how much choice you have there.)

      --
      Software sucks. Open Source sucks less.
    3. Re:Actual text of GPL by ChaosDiscord · · Score: 1

      How did this idiot get moderated up? As I work on my reply, I'm increasingly sure he's a troll. If he's not a troll, then he's really stupid.

      This is how you can get away with releasing only the ORIGINAL code, and not the Linksys mods.

      The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language.

      Think about it. They distributed the source for the "Program" as outlined above. "A work based on the Program" can refer to either the Program (the original) or the "work based on the program" - that is, the derivative. So, if you take it to always mean "The Program" or the ORIGINAL program - then you only must distribute the ORIGINAL PROGRAM and not the mods! Perfectly within the GPL.

      Perhaps, but changing your definition in mid-clause is likely to get you smacked down in a court. That said, here's another quote from the GPL:

      3. You may copy and distribute the Program (or a work based on it, under Section 2)...provided that you also do one of the following:

      Accompany it with the complete corresponding machine-readable source code....

      The corresponding source code would be the code that corresponds with the program you distributed. While it's not the most clear phrasing possible, no other interpretation is reasonable (and the court will support "reasonable" interpretations). Changing your definition of Program midway through would be a no-no.

      The GPL doesn't say you have to release your mods, but only a list of the changes and what dates. Have you actually read the GPL?

      Yup, several times. The GPL quite clearly says you need to release your changes. Anyone foolish enough to try and challenge it on these grounds will get laughed out of the courtroom for clearly trying to play word games. Contrary to popular belief, a contract does not need to be phrased to be resistant to playing word games and other trickery. If the meaning is reasonably clear to all sides involved, it will stand.

      The other problem with the GPL is that there is conjecture and opinion throughout, not fact, as there must be in an Agreement. IANAL but I worked in the world of Contracting (as in Construction) and you must specify everything, not give opinion.

      The first time the GPL gets tried in court it will get thrown out because it's full of opinion, and holes like I just pointed out.

      At least here in the United States, the basis of any agreement is that everyone involved agrees what it means. Your free to sprinkle it with opinions, write it on a napkin, and generally do what you will. If the court believes that both sides agreed on the intent, it's legal.

      All that said, it's irrelevant. "The GPL", as found, say, here, has three distinct parts: A Preamble, the Terms and Conditions, and information using the GPL yourself. Only the Terms and Conditions matter, the rest is just some documentation and suggestions. That documentation tries to spread a message and explain why the Terms and Conditions say what they do. But this preamble and documentation is not the license! I think you'll find the Terms and Conditions extremely straightforward, listing the rules of the game, and with no significant opinions interjected.

      If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

      This is an OPINION that "the best way to achieve this."

  88. Intereference with microwaves by littleghoti · · Score: 1

    So anyone know how this works? the router is operating at 2.4 GHz, and the most common frequency for heating your food is 2.45 GHz. The router is obviously much lower power, so how come it can operate with fcc compliance?

    1. Re:Intereference with microwaves by leshert · · Score: 1

      2.4GHz is an unlicensed chunk of spectrum, much like 900MHz. You can produce whatever you want and use this chunk (which is why microwaves, cordless telephones, wireless networks, and a whole raft of other devices all use it).

      There are a few rules on using it, but it's mostly a free-for-all. And you're right, a running microwave (or a cordless phone) does Bad Things to your throughput when the AP is right beside it.

  89. Re:Why reply to your own post as AC? Dipshiat by Anonymous Coward · · Score: 0

    its funny, laugh!

  90. Speaking as one of the upstream authors... by timbrown · · Score: 2, Informative

    Glad to see the GPL is now being honoured, although this issue would have made an interesting test case.

    I'm a shade confused though, I can't see any good reason why Linksys rebranded from ez-ipupdate to ipupdate.

    Anyway, as far as ez-ipupdate itself goes, the version in the firmware appears to be the same as source that has been released although it is nowhere near the latest version. It doesn't appear LinkSys have made any changes.

    --
    Tim Brown
  91. Come on guy's have some guts by Anonymous Coward · · Score: 1, Interesting

    I don't agree with much of what is said at the beginning of this thread. It is in fact very easy to implement locks in hardware.... the truth of the matter is that Broadcom wanted to create a chip that they would be able to sell into a wide variety of markets including the military. Designing an fab'ing 1 piece of silicon is much cheaper, leaving them to limit the chips capabilities later on in software.

    What I cannot believe is how slow the community has been in reverse engineering the linux wireless drivers contained within the firmware of many of these devices. I purchsed a pair of Belkin 54G AP's at the weekend and within 30 mintues was able to extrace the kernel and root file system which contained amongst other things wl.o the actual driver we all want..... running objdump over this shows us all of the functions and the MIPS3000 assembler code itself, which helps expose how to communicate with the device...... It is not impossible for us to at least attempt to create an open source alternative.....

    Go and download a firmware file yourself (you don't actually need one of the devices) and have a look...

    who's with me?

  92. Re:A wireless network. For a dorm room. by cscx · · Score: 4, Funny

    Apparently he hasn't discovered beer yet.

  93. Re:GPL paradox. by Ibn+al-Hazardous · · Score: 1

    But it seems like the truth is, linksys did because they wanted to be good citizens. The GPL has never been tested in court. It is easy to comply with the terms of the GPL.

    What was that case with MySQL AB now again? I thought it was a matter of taking a GPL violator (NuSphere) to court. Although they did settle, it was firmly on MySQL ABs terms, since NuSphere was going to lose.

    That said, they may have had the option not to release it. The GPL has small teeth: the only real penalty is forced compliance. Though it could be considered copyright infringe.

    Nope. If you break the GPL you lose the right to distribute the piece of GPLed software. So Linksys could be forced to inhibit sales of hardware flashed with Linux, and develop (or licence) replacement software. Does that make good business sense?

    So the question that i see: If linksys did not release the source code, or in anyway comply, what would have happened? Would the coders who wrote the code utilized take legal action? I will not assume the chances of that are.

    Why not? They could have had help from the FSF, like MySQL AB had.

    But for the point, let's say they did. they sued for (x) million dollars.

    Or they could be sued to stop distributing the GPLed softeware.

    snip

    If they are sued Linux will take a hit in terms of market penetration. If they are left alone, the GPL will take the hit.

    Because of the flaws in you reasoning above, I don't think this holds.

    --
    Yes, I am a biological organism. All rumors to the contrary are just that, rumors.
  94. Unnecessary by Jetifi · · Score: 1

    They didn't distribute the compiler, so they don't have to distribute the source.

  95. Still not open by 0x0d0a · · Score: 0

    Sigh. More legalisms on the website, in their Usage Agreement:

    Except as specifically permitted herein, no portion of the information on this Website maybe used, reproduced, broadcast, published or retransmitted in any form, or by any means, without prior written permission from Linksys. You are not permitted nor authorized to modify, distribute, publish, transmit or create derivative works of any materials found on this Website for any public or commercial purpose.

    So the usage agreement states that the usage agreement is the sole authority to license information on the website. Which overrides any GPL licenses included with tarballs.

    1. Re:Still not open by fmu · · Score: 1

      i disagree. specific rule (license attached to specific files on their website) overrides the general rule (usage terms for their website as a whole) in this case

  96. any ethernet (AKA DSL) router running linux ?? by a1bert · · Score: 1

    is there any non wireless router running linux? I do not want to pay for HW I will not use ;)

  97. any ethernet only (AKA DSL) running linux? by a1bert · · Score: 1

    is there any non wireless router running linux? I do not want to pay for HW I will not use ;)

    1. Re:any ethernet only (AKA DSL) running linux? by user32.ExitWindowsEx · · Score: 1

      Check Linksys's products page...they have a LOT of stuff.

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
  98. Maybe they will learn... by Anonymous Coward · · Score: 0

    to avoid the GPL infection.

  99. This reminds me... by TeknoHog · · Score: 2, Funny
    ..of a loonie running around in our physics department, furiously yelling things like "I'll differentiate you!".

    So, this other guy comes along and says, "I'm not afraid of you! I'm e to the x."

    "Well that's just too bad, I'm d/dy!"

    --
    Escher was the first MC and Giger invented the HR department.
  100. Here is the Broadcom Wireless Linux Driver (wl.o) by bensonandhedges · · Score: 1

    Well the symbols anyway

    http://195.18.94.223/symbols.html

  101. It's the VERY least they could do... by OmniGeek · · Score: 1

    Yup, you're right on. Go to their GPL downloads page, and type "busybox.tgz" into the "Search" box at the bottom of the page (about 15 lines below the entry marked 'busybox.tgz'.) The search WON'T find anything. (Why the hell not? Surely the search engine gets tipped off about things it is supposed to index -- or to NOT index?)

    It would be rather hard for Linksys to do less than this; it seems they've gone to some pains to be minimal in their GPL compliance...

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
  102. Offtopic: Amazon affiliate ID's by Anonym0us+Cow+Herd · · Score: 1

    I hate it when people make links on Slashdot to Amazon, and have their affiliate ID embedded in the URL, without bothering to mention it

    Perhaps the slashcode could change the affiliate ID to that of Cowboy Neal?

    --
    The price of freedom is eternal litigation.
  103. GPL Section 7 by Anonymous Coward · · Score: 0
    Which, as it says itself, is redundant, but makes "thoroughly clear":
    If, ...for any other reason...conditions are imposed on you...that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

    If that truly is the case, then they're stuck between a rock and a hard place, and need to start settling copyright infringement suits.

    Yet somehow I don't think it is. They can distribute code plastered with stern warnings "if you change one line of this code, it won't be FCC-spproved and you can't legally broadcast using it", but that doesn't prohibit them from distributing the code so someone else can hack on it and get FCC approval on their hacked-up copy.
  104. great, but what about the WPC54G? by DuckWing · · Score: 2, Insightful

    Great news that they released GPL'd source for the wireless router, but now what about the real need, code/drivers for their wireless cards like the WPC54G? I searched /. for info on it and found an old Ask Slashdot thread, but nothing has improved yet. I wnat drivers for the wireless card dang it!

    --
    -- DuckWing
  105. Re:GPL paradox. by Cyno · · Score: 1

    Lets just hope all companies do what linksys did.

    And what is that? Steal from people, then admit you're wrong months after you were proven to be infringing on someone else's IP. Yeah, let's hope all capitalists act appropriately. Its so typical of greedy white trash.

    This is why I will never buy another linksys or Microsoft or SCO product again. I've drawn a line, anyone else want to cross it?

  106. This is the chip that is in all of the routers by bensonandhedges · · Score: 1

    it's a Broadcom BCM4702, integrated MIP3000 processor PCI 2.2....

    Here's the rub.... it probably can do 802.11a also

    http://www.broadcom.com/products/4702.html

    here is the evaluation board

    http://www.broadcom.com/cgi-bin/pr/prps.cgi?pr_i d= PR020910

  107. The BEFW11s4 has 5 versions that i'm aware of. by j-stroy · · Score: 1

    I have one of these units.. it performs much better with an antenna upgrade! Someone at Linksys seems to be doing some good engineering, because their gear is cheap, functional and has hackable connectors. The downside is some firmware features which i would love to have for handling MAC filtering/redirecting dynamically. The bios upgrades they offer seem hardware version specific.. the BEFW11s4 has 5 versions that i'm aware of. (1, 2, 3, 3.2, 4)

    1. Re:The BEFW11s4 has 5 versions that i'm aware of. by SirDrinksAlot · · Score: 1

      Really the only difference between the differnt versions is minor hardware changes, 2 to 4 are minor hardware changes, 1 just doesnt have multi spectrum antenna configurations. on 1 you cant set left or right antenna or both. on 2-4 you can have left, right, or both.
      i dont know the difference between 2 3 and 4 tho. 1 and 2 is just the antenna config and powersupply. the BEFW11S4 has a better powersupply and doesnt blow up.

  108. Either buy their products, or don't. by dstone · · Score: 1

    If you use there products, shoot them a quick email to say 'thanks'.

    I've thanked them in the most meaningful way to possibly thank a corporation: I've purchased their products when their products are worthy. They are required to comply with the GPL. Thanking parties for not breaking licensing terms they've agreed to or contracts they've signed seems like unnecessary praise.

  109. external antenna? by praedor · · Score: 1

    I've looked at the GPL/sourceforge driver for the Atheros chipset and its device support list is extremely short at this time. It lists only 2 802.11g devices (cardbus), the rest are 802.11a devices. Of these 802.11g clients (Netgear and some other gizmo) neither had an external antenna capability. Are there any 802.11g cards with an adaptor for an external antenna?


    If the sourceforge driver will work, great, but I would like a card that has an external antenna attachment rather than have to hack the card and add one on, potentially wrecking it in the process.

    --
    In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
  110. NEW! Evidence of ongoing GPL violation by bensonandhedges · · Score: 1

    Hi, i've just ripped this out of the broadcom/linksys/belkin kernel

    are these on GPL'd modifications a violation?

    "Linux version 2.4.5 (hyin@cactus.localdomain) (gcc version 3.0 20010422 (prerelease) with bcm4710a0 modifications) #3 Wed Jun 4 17:12:54 PDT 2003"

    1. Re:NEW! Evidence of ongoing GPL violation by ryanr · · Score: 1

      They would be, if they shipped a gcc binary. The GPL doesn't require you to produce changes you use in house, only if you supply the binaries to someone else do you have to give up the source.

      Ask them for a binary copy of their compiler. :)

  111. No such luck by CausticWindow · · Score: 3, Funny

    with the Barricade I've got from SMC (it's got Linksys firmware).

    The firmware .bin is an arj'ed file, but the only thing of interest in the unpacked file is this string:

    Hey Moe, it dont woik. NYUK NYUK NYUK NYUK *bop* Owww!

    In the WRT54G, one of the first strings is:

    piggy

    Hm

    --
    How small a thought it takes to fill a whole life
  112. Kernel source is not complete by teengoat · · Score: 1
    The Linksys box is based on a Broadcom MIPS processor. In addition to the compiler not being released, they have not released the board support package for the platforms. Here's a snippet from arch/mips/config.in
    bool 'Support for Broadcom MIPS-based boards' CONFIG_MIPS_BRCM
    dep_bool 'Support for Broadcom BCM93725' CONFIG_BCM93725 $CONFIG_MIPS_BRCM
    dep_bool 'Support for Broadcom VideoJack' CONFIG_BCM93725_VJ $CONFIG_BCM93725
    dep_bool 'Support for Broadcom BCM93730' CONFIG_BCM93730 $CONFIG_MIPS_BRCM
    dep_bool 'Support for Broadcom BCM933XX' CONFIG_BCM933XX $CONFIG_MIPS_BRCM
    dep_bool 'Support for Broadcom BCM947XX' CONFIG_BCM947XX $CONFIG_MIPS_BRCM
    if [ "$CONFIG_BCM947XX" = "y" ] ; then
    bool ' Support for Broadcom BCM4710' CONFIG_BCM4710
    bool ' Support for Broadcom BCM4704' CONFIG_BCM4704
    bool ' Support for Broadcom BCM94702CPCI' CONFIG_BCM94702_CPCI
    fi
    Now here's some more stuff from arch/mips/Makefile:
    #
    # Broadcom BCM947XX variants
    #
    ifdef CONFIG_BCM947XX
    SRCBASE := $(TOPDIR)/../..
    CFLAGS += -I$(SRCBASE)/include
    LIBS += arch/mips/brcm-boards/bcm947xx/bcm947xx.o arch/mips/brcm-boards
    /generic/brcm.o
    SUBDIRS&nb sp; += arch/mips/brcm-boards/generic arch/mips/brcm-boards/bcm947xx
    LOADADDR += 0x80000000
    TEXTADDR += 0x80001000
    endif

    #
    # Broadcom BCM933XX variants
    #
    ifdef CONFIG_BCM933XX
    LIBS += arch/mips/brcm-boards/bcm933xx/bcm933xx.a
    SUBDIRS += arch/mips/brcm-boards/bcm933xx
    LOADADDR += 0x80010000
    endif
    Now where's the source for arch/mips/brcm-boards ? these are not loadable modules so Linksys and Broadcom are both in violation of the GPL and the special "loadable module" concession of the Linux kernel.
  113. Just sent an email to opensource@linksys by bensonandhedges · · Score: 1

    Just sent this:

    Hi,
    you have recently open sourced the kernel supplied by broadcom for the
    WRT54G. Unfortunately after examination you have not included all of the
    source. In fact functions such as bcm_atoi, bcm_ctype, bcm_ether_atoe,
    bcm_ether_ntoa, bcm_mdelay, bcm_parse_tlvs and bcm_strtoul seem to be
    missing. In addition the specific BCM4710 memory management code, which is
    in the binary kernel, is not there. There are numerous other examples.

    More concerning is the version of gcc used to compile the kernel, this
    identifies itself as "gcc version 3.0 20010422 (prerelease) with bcm4710a0
    modifications" but no such modification have been submitted to GNU as far as
    I am aware. Could you please clarify this and, if I am right, correct it.

    The delivery reciept gave up these names:
    > Your message

    To: opensource@linksys.com
    Subject: Open source kernel for WRT54G
    Sent: Mon, 7 Jul 2003 11:07:50 -0700

    was delivered to the following recipient(s):

    Ben Sakai on Mon, 7 Jul 2003 11:09:23 -0700
    MSEXCH:MSExchangeMTA:US:MAIL
    Vito Sansevero on Mon, 7 Jul 2003 11:09:23 -0700
    MSEXCH:MSExchangeMTA:US:MAIL
    Chris Chapman on Mon, 7 Jul 2003 11:09:23 -0700
    MSEXCH:MSExchangeMTA:US:MAIL

    worth giving them a call?

  114. What's the work? Johannes... burk! by morgue-ann · · Score: 1

    Did you really expect them to release proprietary intellectual property?

    I sure do, because I read the GPL as requiring it.

    GPL:

    This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications....

    In TiVo's case, people seem to go along with TiVo's claim that "the work" is the modified kernel which TiVo does provide source for.

    I think "the work" is the whole box. What good does a modified kernel do without the apps on that box. Are the apps "merely aggregated" (GPL's exception for derivative works) with the kernel? Not in such a closed box (no "ls" to see those parts and these parts).

    What's Linksys's "work?" Once again, I claim it's the whole access point/router. They don't sell the kernel binary by itself and firmware updates are distributed with GPL and proprietary code in one lump (maybe not statically linked, but I don't think that's a reasonable exception).

    credit where it's due

  115. Re:GPL paradox. by johnnyb · · Score: 1

    What you miss is that you are only obligated to follow the GPL if you redistribute code outside of your organization. Period. If you don't redistribute code outside of your organization, you don't have to pay ANY attention to the GPL at all.

    With other software licenses, you have to accept them to _use_ the software. With the GPL, you can use it without accepting the license agreement. The GPL _broadens_ your rights, it doesn't restrict them.

    This is what proprietary companies don't want you to know, because then it shows that _proprietary_ software is what you need legal departments for, while open-source only requires one for redistribution outside of your organization.

  116. here are the kernel strings by bensonandhedges · · Score: 1

    http://195.18.94.223/ls.str

  117. Re:GPL paradox. by booch · · Score: 1

    Yes, it is easy to comply with the GPL. That's kind of the point.

    And as a matter of fact, the author of BusyBox, which is used in the LinkSys WAP, was taking actions to sue LinkSys for this violation. I'm not sure if he's proceeding with that now that they've released the code. The GPL really doesn't say that you can comply after the fact and get away with it. It says that you must comply in order to distribute the program.

    As far as worried about being sued for using GPLed code, I fail to see how it's any different than being sued for using proprietary code. Try taking some of Microsoft's code without following their contracts and see how far you get. I don't see how Microsoft would lose market penetration if they were to sue somebody for using their code without permission.

    The only paradox I see in suing for violations of the GPL, is the fact that there's very little direct damages caused by distributing it. You probably can't expect to get much more than statutory damages. To do that, you'd have to register your copyright with the Library of Congress, and you'd only get $100,000 at the most.

    BTW, technically there is no such thing as a violation of the GPL. Either you implicitly agree to it by following it, or you implicitly disagree with it by not following it. If you disagree with it, it does not apply. Instead, default copyright law applies. So if you do not agree to the GPL, you are violating copyright law, not the GPL. (It's hard to violate a contract you never agreed to.)

    --
    Software sucks. Open Source sucks less.
  118. Re:GPL paradox. by Anonymous Coward · · Score: 0

    Take your racist comments off of Slashdot. You have freedom of speech, but no hate speech rights here. If you post again like this Cyno, Slashdot will be asked to filter you.

  119. uhhhhh by Anonymous Coward · · Score: 0

    and how often do you stick LSD up your ass?

  120. What about other Linux products - Netgear, etc by PhilipJLewis · · Score: 1

    I have a Netgear Wireless Access Point WG602 (802.11g/b - current) - this runs Linux - no mention of this anywhere on their support or download site. Seems also to use GPL'ed code - Don't upgrade to the latest version (1.5.xx) or you'll not be able to telnet into it... Funny they released a version without command line capability after the Linksys affair!

    What about Watchguard - all of their vClass and Firebox III firewall appliance range use Linux with GPL'ed bits and pieces - they used to provide the GPL'ed bits on a website for the FireboxII range a few years ago - now that seems to have gone away?!

    Phil

    1. Re:What about other Linux products - Netgear, etc by oskus · · Score: 1

      I checked out Buffalo firmware's for WBR-G54 and WLA-G54 accesspoints and they also contains cramfs image. http://www.buffalotech.com/wireless/downloads/firm ware/WLAG54_final.zip
      cramfs image starts at 0xC002F
      http://www.buffalotech.com/wireless/downloads/firm ware/WBRG54_final.zip
      cramfs image starts at 0xC0022
      It clearly shows that Broadcomm has distributed reference design for accesspoint to all hardware makers with source and modified GCC compiler.

  121. Actual text of the GPL by penguinrenegade · · Score: 1

    From Dictionary.com:

    either: The one or the other. Not BOTH.

    a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications

    Your interpretation of this to not mean both is pretty shaky. Try replacing the word "either" with the word "both" in the text. That'd mean that a derived work is 2 separate things. Besides, Section 2 of the GPL is effective even without the definition of "work based on the Program":


    either: The one or the other. Not BOTH.

    So replacing the word either with the word both is automatically exclusionary. BOTH means BOTH, either means ONE OR THE OTHER. SO, you can easily interpret it to mean ONE OR THE OTHER. That is what either means. A lawyer might have written it, but that is EXACTLY what it says. At the beginning. SO, if you take the word either to mean either the Original Program OR (can I emphasize OR enough here?) the derivative work, all you have to do is release a) the original source, since it can be one OR the other, and a LIST (it says specifically only the list) of the mods.

    Search Microsoft copyrighted code and you'll find UC Regents in there - BSD Unix. They've copyrighted BSD code that they co-opted. Try it sometime. You're off base, and just want to prove that you're right, instead of actually looking at what the words mean. Trying to substitute "both" for "either" means that either doesn't mean both, by your definition. Give it up already.

    1. Re:Actual text of the GPL by booch · · Score: 1
      Apparently you didn't read the whole entry on dictionary.com! Here's one of the parts you missed:

      One and the other; each: rings on either hand.

      See the and in there? ;)

      You're off base, and just want to prove that you're right, instead of actually looking at what the words mean.

      Actually, I don't think "either" matters that much, since I think section 2 still holds under the conventional interpretation even if your argument about "either" holds. You didn't seem to address that part of my argument. You'll also note that there's not a lot of support for your interpretation of the wording. (You could make the argument that it's because everyone on Slashdot is pro-GPL, but there are always people here willing to stand up to convention. Also, I've not seen anyone on other sites supporting your interpretation.)

      Despite what you may believe, words are almost always a little vague, and subject to some interpretation. Even in carefully-worded contracts. I think you have shown that the wording in question can be interpretted in more than one way. I just don't think that a judge is likely to find your interpretation more valid than the conventional interpretation.

      Search Microsoft copyrighted code and you'll find UC Regents in there - BSD Unix. They've copyrighted BSD code that they co-opted.

      I'm not sure where you're going with that. Yes, I'm fully aware that Microsoft includes code derived from BSD. But the BSD license allows anyone to "co-opt" the code and incorporate it into proprietary copyrighted code. As it happens, I also have a CD with some GPLed code distributed by Microsoft -- GNU utilities from their Windows Resource Kit. (I find that especially interesting given Microsoft's FUD a year or so back that using GPLed code would cause you to have to GPL all your code.)

      Try it sometime.

      I'm not sure what I'm supposed to try. Co-opting BSD code and adding some of my copyrighted code to it?

      --
      Software sucks. Open Source sucks less.