Slashdot Mirror


Novell Cancels BrainShare Conference

A.B. VerHausen writes "While OSCON and SCALE organizers ramp up plans for their events, Novell shuts down BrainShare after 20 years, citing travel costs and budget tightening as main concerns. 'Instead of the traditional in-person conference, Novell plans to offer online classes and virtual conferences to make education and training available to more people at a lower per-head cost to companies,' says the news story on OStatic.com."

20 of 102 comments (clear)

  1. Huh? by girlintraining · · Score: 3, Funny

    I think the real story here is people are still using Novell. They must be found and stopped! Oh god, the nightmares of NetBEUI and IPX/SPX... they haunt me.

    --
    #fuckbeta #iamslashdot #dicemustdie
    1. Re:Huh? by Gr33nNight · · Score: 3, Interesting

      We have a Novell backend, and use Groupwise and Zenworks. We do not use NetBEUI or IPX/SPX.

    2. Re:Huh? by spun · · Score: 3, Informative

      We use a Novell back end for file and print services. You know it's all based on Suse Linux now, right? Novell dropped Netware last year, I think. Almost all of last year's Brainshare was about Linux. Good times, I'm sad to see it go.

      --
      - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    3. Re:Huh? by Anonymous Coward · · Score: 3, Funny

      We use a Novell back end for file and print services. You know it's all half-assedly based on Suse Linux now, right? Novell dropped Netware last year, I think. Almost all of last year's Brainshare was about half-assed Linux. Good times, I'm sad to see it go.

      Here, I just wanted to make some snide half-ass remark using a tired Internet meme to feel superior and smug without any actual work or knowledge on my part.

      There, fixed that for you...

    4. Re:Huh? by IBBigPoppa · · Score: 3, Informative

      Novell has moved so far passed Netware, IPX, and NetBEUI. They actually have the second largest Linux distro, Suse Linux. Gardner has rated their Identity Manager Solution as a leader. They also own PlateSpin and Managed Objects. They are not the Novell most remember from Netware 5.0 and 6.0. They are have some interesting stuff like Dynamic Storage (policy based storage management) and Domain Services for Windows (AD integration/emulation with eDirectory and Linux).

    5. Re:Huh? by garcia · · Score: 3, Funny

      We have a Novell backend, and use Groupwise and Zenworks.

      I'm sorry.

    6. Re:Huh? by causality · · Score: 3, Funny

      We use a Novell back end for file and print services. You know it's all half-assedly based on Suse Linux now, right? Novell dropped Netware last year, I think. Almost all of last year's Brainshare was about half-assed Linux. Good times, I'm sad to see it go.

      Here, I just wanted to make some snide half-ass remark using a tired Internet meme to feel superior and smug without any actual work or knowledge on my part.

      There, fixed that for you...

      Are you sure that's the way to go about it? Tired internet memes usually get rewarded (modded up) around here. All you need now are some pants, hot grits, Natalie Portman, sharks with lasers on their heads, flying chairs, the ability to imagine a Beowulf cluster of those, and maybe some frosty piss.

      --
      It is a miracle that curiosity survives formal education. - Einstein
    7. Re:Huh? by Anonymous Coward · · Score: 2, Funny

      I used a tired Internet meme to mock the tired Internet meme. The recursive nature alone is worth points. And I didn't have to work or contribute anything on my part. More recursion - profit!

    8. Re:Huh? by paesano · · Score: 3, Informative
      Please don't blame NetBEUI on Novell. That is Microsoft's atrocity. Last I checked, they still use that crap tunneled in TCPIP.

      Perhaps you meant NCP?

    9. Re:Huh? by KillerBees · · Score: 2, Funny

      They are not the Novell most remember from Netware 5.0 and 6.0..

      Apparently not a lot of people remember the modern Novell either...

  2. Re:Netware? by IceCreamGuy · · Score: 3, Informative

    Yes. I run Netware 5 on HP LC3s. They have been up and running since 1998. We're migrating to AD right now. Get off my case!

  3. IPX was actually a very nice protocol by Terje+Mathisen · · Score: 4, Informative

    Disclaimer: I spent a year (91-92) working for Novell in Utah.

    That said, IPX was in many ways both more forward-looking and easier to administrate than IP networks:

    Instead of statically allocated local addresses or DHCP servers, IPX use the 48-bit MAC address as the only local identifier.

    IPX and IP both use 32-bit external addresses, but the IPX 32-bit address is simply the address of the network, with no addressing mask to split it into net/host parts. This meant that clients could be plugged in anywhere and just worked, without any DHCP servers, and since each Netware server was allocated its own internal 32-bit network address, it was trivial to install multiple network cards for load balancing and/or redundancy:

    If a single link went down, all traffic would automatically be rerouted to the other interface, while having a single unique server address.

    This same mechanism was a key part of Software Fault Tolerant (SFT) NetWare, which used a mirrored (over a separate fast/high-bandwidth link) link to replicate all inputs between two servers: This allowed Drew Major (the chief architect) to keep the two servers in lockstep, and handle pretty much any kind of single disaster (up to and including smashing a server with a 100-ton press) without a single client drop.

    As a programmer I really liked the way IPX used Async Event Blocks (AEBs) to control all send/receive operations, with optional application callbacks at interrupt time.

    At one point (around 1988?) this allowed me to write an IPX-based print server under Dos, which managed to fit a dual-buffered print receiver, interrupt-driven serial and parallel port printer interfacing plus all the housekeeping needed for a TSR, inside about 1600 bytes.

    This allowed 2x512 bytes as print buffers, 256 bytes as the local stack and about 300+ bytes for all the remaining code and data.

    Terje

    --
    "almost all programming can be viewed as an exercise in caching"
    1. Re:IPX was actually a very nice protocol by dedazo · · Score: 2, Interesting

      Agreed. There was nothing wrong with IPX at all. The standardization on TCP/IP and the death of other packet protocols is not so much going for something "better", but rather for the least common denominator. Not that that's particularly bad, since it's important for a more open internet and better interop, but it doesn't take away anything from the technical value of other implementations.

      Anyone remember LANtastic? As long as you didn't use Token Ring it was pretty good as well.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    2. Re:IPX was actually a very nice protocol by Anonymous Coward · · Score: 3, Funny

      Whoa! OK, I'll get off your lawn.

    3. Re:IPX was actually a very nice protocol by IGnatius+T+Foobar · · Score: 3, Interesting

      Instead of statically allocated local addresses or DHCP servers, IPX use the 48-bit MAC address as the only local identifier. IPX and IP both use 32-bit external addresses, but the IPX 32-bit address is simply the address of the network, with no addressing mask to split it into net/host parts. This meant that clients could be plugged in anywhere and just worked, without any DHCP servers, and since each Netware server was allocated its own internal 32-bit network address, it was trivial to install multiple network cards for load balancing and/or redundancy

      Yup. And now there's a push for IPv6. Automatic address assignment on IPv6 turns the 48-bit MAC address into a portion of the IPv6 address. It's startlingly similar to IPX. If the Internet had been based on IPX, and they figured out a way to make IPX run at a global scale (finding equivalents to things like BGP) we wouldn't be in the impending address exhaustion pickle we are today.

      --
      Tired of FB/Google censorship? Visit UNCENSORED!
    4. Re:IPX was actually a very nice protocol by virtue3 · · Score: 2, Interesting

      Uh... guys, it's called UDP, which has pretty much entirely replaced IPX. Mostly because it's the same protocol more or less running through IP. It saves you from having to install multiple network interfaces on your system. And it's all going through the same layers. That and UDP can work through NATS/Firewalls, which I'm not totally sure IPX did successfully (at least back in teh day when I was still learning how to use port forwarding when I was playing star craft games over a LAN).

  4. Not to mention... by Quiet_Desperation · · Score: 4, Funny

    ...the whole sharing brains thing was just too messy. Everyone always went home all sticky.

    Eew.

  5. The real problem by Bearpaw · · Score: 3, Funny

    ...the whole sharing brains thing was just too messy. Everyone always went home all sticky.

    The real problem was all the zombie processes.

  6. Half-Assed Truths by TheNinjaroach · · Score: 4, Informative

    I agree that the parent was making some snide half-assed remarks towards Novell / SuSE Linux, but in those remarks were some half-assed truths.

    We're migrating off of the last of our Netware boxes, some of them have over four years of uptime so we're not exactly rushing to swap them out. Many of these boxes are being replaced with their new SUSE Linux-based counterparts that offer the same Netware file and directory services that we had before. So far the experience has been terrible. Large file servers that never crashed on Netware now go down weekly. Directory services simply stop answering LDAP queries with no explanation. Sometimes we can restart the service without rebooting, but usually a poorly implemented kernel module blows out and takes the whole system down with it.

    We aren't suffering from problems with Linux, instead we suffer from Novell rushing ported Netware services out the door to make their SUSE offerings look like a complete and competent replacement for Netware. They're not there yet, so I find some truth to the parent's troll that "it's all half-assedly based on Suse Linux now," because in many ways it is.

    --
    I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
    1. Re:Half-Assed Truths by drspliff · · Score: 2, Interesting

      I used eDirectory on Linux and Netware and it every now & then we'd login to one of the main directory boxen and see the whole console filled with abends. As far as file-serving went it was absolutely rock solid, but never managed to see how it fared on Linux (I left the company when they were still using nw6.5 and unitedlinux/sles) because we just didn't "trust" it when our existing setup worked fine.

      I don't know how far they've gotten along with making SuSE more streamlined, but at the time most of our Linux installs were authenticating against the eDirectory servers via LDAP, whenever these went down nss_ldap, pam_ldap and friends would fsck up completely until rebooted... (it would hang forever logging in, even as `root`).

      Their whole approach seems to be trying to weigh the monetary cost of each option, keeping netware alive vs using linux, adopting to linux vs "trusted" stability and so on... not a position I'd like to be in.