1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Busybox 1.9.0 UNSTABLE

Discussion in 'Tomato Firmware' started by BassKozz, Jan 18, 2008.

  1. BassKozz

    BassKozz Network Guru Member

    I posted this in the "Official Tomato v1.14.1288 released" thread here, but didn't get any feedback, so here it is again...

    According to Busybox.net:
    Should I be concerned?
     
  2. Kiwi8

    Kiwi8 LI Guru Member

    Well if your router is used in a way that is critical for your business or a matter of life and death, then probably not. Otherwise just flash away. :)
     
  3. FRiC

    FRiC LI Guru Member

    It just means 1.9.0 is the very newest bleeding edge version and could have bugs. It doesn't mean that it's literally unstable.
     
  4. wahur1

    wahur1 LI Guru Member

    *n00b question*

    What is Busybox? :redface:
     
  5. der_Kief

    der_Kief Super Moderator Staff Member Member

  6. Kiwi8

    Kiwi8 LI Guru Member

    It is the commandline OS that is running when u telnet into the router that's flashed with Tomato. :)
     
  7. Maggard

    Maggard LI Guru Member

    You didn't get any feedback... in 24.something hours.

    "Unstable" is a Developer term for new code. It doesn't mean the code is literally unstable, just that it hasn't been tested out in the real world and empirically determined "Stable" ie significantly free of bugs. You'll find that most publicly available code developments have "Unstable" & "Stable" release branches, with "Stable" typically lagging by a few weeks or months.

    Unless there are reports of problems this release of Busybox appears stable enough for Tomato & Tomato-user's needs. If you are depending on more esoteric features of Busybox for some unusual purposes you should be aware that they've possibly not been tested as thoroughly as in "Stable" releases and may indeed exhibit unexpected results.

    However given that you're not already well-familiar with the terms "Stable" & "Unstable" in reference to code branches it's unlikely you'll be exercising Busybox that thoroughly. Therefore any bugs in Busybox in relation to Tomato usage will most likely be discovered & documented well in advance for you by others.

    - Or -

    Jon felt this release of Busybox robust enough for inclusion in his latest Tomato; if you're going to trust his judgement on other matters you may as well trust it in this one too. If there is a problem we'll likely hear of it soon enough.
     
  8. BassKozz

    BassKozz Network Guru Member

    oh look a fellow masshole, thanks for the snoody Wellesley remarks, j/k ;)
     
  9. z00100

    z00100 LI Guru Member

    I probably wouldn't sweat it. Of course unless this is used in a "critical" environment.
     
  10. szfong

    szfong Network Guru Member

    Don't worry about the "unstable" designation. It's a relative term. I've runned so called "stable" releases of various software/firmware in the past and they "stank". And the "unstable" versions were in reality "quite stable". So, this release looks good so far.
     
  11. Sopmod

    Sopmod Network Guru Member

    Unstable .... it could mean life or death just the same as ...

    "Scotty there are lots of vibrations"

    "Aye Captain, she's unstable. She wasn't built for this. I not sure how much more she can take."
     
  12. szfong

    szfong Network Guru Member

    So far it's quite stable on several of my WHR-HP-G54, can you please enlighten us and tell us what issues you are having?
     
  13. UltUlt

    UltUlt LI Guru Member

    I'm with BassKozz on this one.
     
  14. LLigetfa

    LLigetfa LI Guru Member

    Which is what?
    In the absence of any public beta process for Tomato, how do you classify Tomato? Stable, Testing, or Unstable?
     
  15. der_Kief

    der_Kief Super Moderator Staff Member Member

    Stable or unstable, that's the question :argue:
     
  16. LLigetfa

    LLigetfa LI Guru Member

    My Debian roots are showing. :redface:
     
  17. Slavedriver

    Slavedriver LI Guru Member

    That would be stable for previous release and unstable for current :)
     
  18. LLigetfa

    LLigetfa LI Guru Member

    It was a rhetorical question.
     
  19. Slavedriver

    Slavedriver LI Guru Member

    I know :)
     
  20. BassKozz

    BassKozz Network Guru Member

    There is alot of talk in the "Official Tomato v1.14.1288 released" thread about syslogd and udhcpc issues, which are directly related to Busybox...
    could Busybox be the cause of this new firmware's issues?
     
  21. BassKozz

    BassKozz Network Guru Member

    Don't say I didn't warn you ;)
     

Share This Page