Slashdot Mirror

← Back to Domains

Domain: freaks-unidos.net

Stories and comments across the archive that link to freaks-unidos.net.

Comments · 12

  1. Re:Realtime, VxWorks, Dolla Dolla Bill Yall by necio_online · · Score: 1 · on Linux Gains Native RTOS Emulation Layer

    I've played with the Linux realtime extensions (preempt_rt) in a production environment and so far I've had good results. This is a very simple usleep test that shows how having the patch helps: http://wiki.freaks-unidos.net/weblogs/arhuaco/preempt_rt-test You can use the SCHED_RR or the SCHED_FIFO scheduling algorithm for realtime applications.

  2. Same guy behind boycottnovell.com? by Azul · · Score: 1 · on How Microsoft-Yahoo Will Affect Open Source

    A quick search reveals that this Roy Schestowitz is the same guy behind boycottnovell.com (though the domain's registers don't seem to match those for schestowitz.com).

    I don't know about you but for me this removes a lot of credibility from his claims (which, in good Slashdot fashion, I haven't read). I always found boycottnovell.com extremely FUDish (even though I, for many reasons, didn't like the Novell-MS agreement). The whole Novell-MS agreement taught me that some people from the Free Software or Open Source community will spread as much FUD as MS, or try to.

    I'm not trying to make an ad hominem argument, just thought I'd mention who the guy was --as even if you disagree with my opinion of boycottnovell.com, I suppose you'll find this info useful.

    Disclaimer: I used to work at Novell at the time but now I don't. I've been critical of many decisions by Novell (including the agreement with MS). Nowadays I work for the main competitor the eventual Microhoo would have.

  3. Same guy behind boycottnovell.com? by Azul · · Score: 1 · on How Microsoft-Yahoo Will Affect Open Source

    A quick search reveals that this Roy Schestowitz is the same guy behind boycottnovell.com (though the domain's registers don't seem to match those for schestowitz.com).

    I don't know about you but for me this removes a lot of credibility from his claims (which, in good Slashdot fashion, I haven't read). I always found boycottnovell.com extremely FUDish (even though I, for many reasons, didn't like the Novell-MS agreement). The whole Novell-MS agreement taught me that some people from the Free Software or Open Source community will spread as much FUD as MS, or try to.

    I'm not trying to make an ad hominem argument, just thought I'd mention who the guy was --as even if you disagree with my opinion of boycottnovell.com, I suppose you'll find this info useful.

    Disclaimer: I used to work at Novell at the time but now I don't. I've been critical of many decisions by Novell (including the agreement with MS). Nowadays I work for the main competitor the eventual Microhoo would have.

  4. Re:Perspectives by Azul · · Score: 1 · on Perspectives on Spamhaus's Dilemma
    You say you are a "small email service provider" with 75 million email addresses? A simple google search shows that an email service provider with even 10 million email addresses can't be called "small" by any stretch of the word.

    The sbl-xbl list stops ~ 80% of our spam. [...] Bayesian doesn't stop spam. It just flags stuff as possible spam.


    Both Bayesian algorithms as well as sbl-xbl checks are just methods to flag a message/SMTP-transaction as possible spam. What you do after those checks is (eg. drop the message altogether, flag it somehow so the MUA shows it differently) could be claimed to be the difference between "stopping" and "flagging" spam. But make no mistake, sbl-xbl and Bayesian methods are the same kind of things: methods to check a message/SMTP-transaction and see if it is likely spam. How would, for example, automatically dropping messages with a 80% probability of being spam not be "stopping spam"?

    That said, I think the best approach is the one used by SpamAssassin, of associating different scores to each of the tests that can be used to distinguish spam from ham. The scores are found using neural networks. While this has the minor disadvantage of requiring the message to be transported to your server (instead of being able to reject it as part of the SMTP transaction), it should have the highest reliability as far as picking spam from ham does. Usually I drop messages with a really high score, store messages with a high score in a separate per-user "Spam" folder and store the rest in the users' regular inbox.

    Hmm, in case anyone is interested, I'm starting to write down a draft about how I setup my servers to do this using Debian and free software.
  5. Re:I always wondered... by Anonymous Coward · · Score: 0 · on LDAP Authentication in Linux

    May be you'll find this introductory document useful:

    http://wiki.freaks-unidos.net/ldap-intro

  6. Our wiki Linux LDAP Howto by Anonymous Coward · · Score: 3, Informative · on LDAP Authentication in Linux

    I figured this was as good time as any to point out our relatively complete Linux LDAP HOWTO, which covers quite a few LDAP servers (MS AD, Novell eDir, OpenLDAP) and the security implications of different setups (eg. using PAM_LDAP vs just using NSS_LDAP). The article lives in a wiki so any improvements are welcome. :-)

    I hope you find it useful.

  7. Re:Wiki + CVS/SVN? by Anonymous Coward · · Score: 0 · on More Wiki Than Ever
    Are you familiar with svnwiki?

    There. :-)

  8. Svnwiki, of course by Azul · · Score: 5, Interesting · on Document Management and Version Control?

    I would suggest using svnwiki, a wiki system that stores its whole contents in a Subversion repository (Disclaimer: I am the main author of svnwiki). That allows you to use the usual svn commands (svn diff, svn log, svn update, etc.) to work with your wiki as well as using the web interface.

    You can see an example wiki (in spanish) and its associated svn repository (login as anonymous, password is the empty string; Slashdot seems to strip out this auth information from my URL) to get an idea of what the repository looks like.

    These are examples of some of its features:

  9. Svnwiki, of course by Azul · · Score: 5, Interesting · on Document Management and Version Control?

    I would suggest using svnwiki, a wiki system that stores its whole contents in a Subversion repository (Disclaimer: I am the main author of svnwiki). That allows you to use the usual svn commands (svn diff, svn log, svn update, etc.) to work with your wiki as well as using the web interface.

    You can see an example wiki (in spanish) and its associated svn repository (login as anonymous, password is the empty string; Slashdot seems to strip out this auth information from my URL) to get an idea of what the repository looks like.

    These are examples of some of its features:

  10. Re:SuSE is *not* Open Source! by Azul · · Score: 1 · on Novell To Open Source SUSE
    Moderators: parent post is spreading false information, please don't moderate as Informative. Here is why.

    That Novell allows you to redistribute it does *not* mean that you can actually redistribute it.

    The text you quote says: "Your license rights with respect to individual components accompanied by separate license terms are defined by those terms; nothing in this Agreement (including, for example, the "Other License Terms and Restrictions," below) shall [...] otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under such license terms."

    There are some proprietary packages included in SuSE Professional that you are not allowed to redistribute (consult the list of packages). Here are two examples:

    • Sun's Java JRE's license specifies that redistribution of this software is only allowed if it is "bundled as part of, and for the sole purpose of running, your Programs". Making a copy of the JRE as part of an entire copy of a GNU/Linux distribution seems to serve a different purpose.
    • Acrobat Reader's license allows you to redistribute the software but requires you to keep no copies: "You may not, rent, lease, sublicense, assign or transfer your rights in the Software, or authorize all or any portion of the Software to be copied onto another user's computer except as may be expressly permitted herein. You may, however, transfer all your rights to Use the Software to another person or legal entity provided that: [...] (b) you retain no copies, including backups and copies stored on a computer [...]".


    I haven't looked at their licenses but I suspect there could be additional problems with Opera, RealPlayer, TextMaker, PlanMaker, all included in SuSE Professional 9.3.

    As a consequence, if you give copies away, even if you don't charge for them, you'd be violating these packages' licenses.

    So, in short, no, you can not give it away.

    If you want more details, please do read the post in my weblog I mentioned in the grandparent post. Feel free to point out errors after you've read it and I'll update it.
  11. Re:SuSE is *not* Open Source! by Azul · · Score: 1 · on Novell To Open Source SUSE

    Erm, that link is http://azul.freaks-unidos.net/posts/Questions%20Ab out%20SuSE%20Licensing.html, of course.

  12. Re:The real question: binary compatibility by Azul · · Score: 3, Informative · on Novell To Open Source SUSE

    The only reason I can think for them not to be entirely compatible is that SuSE Professional is released much more frequently than SLES. SLES 9 Sp2, for example, comes with a kernel based on 2.6.5 (with lots of fixes by Novell) and this will continue for the entire lifespan of SLES 9. This doesn't happen with SuSE Professional, which has an entirely different focus and is based on the latest available versions of all packages.

    In order for them to be compatible, you'd need to drop the stability of SLES, which would be a stupid move, or stabilize SuSE Professional (rather than build it using the latest available versions of software), which would be a stupid move as well.

    Providers of propietary software do certify it against specific distributions (and even versions). This is a process that takes time and money from them, so its a smarter move to certify against the stable distribution, not the constantly moving one, specially since their creator does not offer support for the latter.

    And, anyway, you can legally run SLES for as long as you want without paying Novell (see this post in my weblog for more information)

    So no, there are real reasons why they are not compatible and they are not your simplistic "they don't want them to be" ideas.