Slashdot Mirror


User: hagan

hagan's activity in the archive.

Stories
0
Comments
7
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 7

  1. Re:What could take this down... on Worldcom's Frame Relay Down · · Score: 2

    lots of things could keep this down. i'm wondering if their "upgrade" was an emergency last ditch effort to fix things. i'm betting that this will all come down to a bad piece of hardware/software which has a failure mode that is protocol correct (remember the zost cost route stuff from way back?). goes back to the old "your secondary systems should be different location, different hardware, and different vendors (e.g. if you use sun, fail to dec/hp/etc). of course many companies will whine that the QA cost is too high :) the sad thing is that they don't seem to be willing to take public responsibility for the failure, much like an auction company that seems to point blame at everyone except themselves.

  2. Re:Scaling the box might be the real problem... on Ask Slashdot: Building a Large Email Service · · Score: 1

    Look into postfix, it actually does a very good job of utilizing MP systems. the trick is to have many processes loosely managed which communicate with eachother (rather similar to a multithreaded design, all in where you share the ram, really).

  3. Dual Celerons easier than ever...what crap on Ask Slashdot: Is SMP worth it? · · Score: 1

    um, you are quite wrong. My dual celeron 450/100
    machine will back me up with this. It works,
    and works WELL. you need to unmess up the
    glue logic which intel left disconnected
    so that one wouldn't use their celeron in
    dual mode.

  4. Cachedot Curiosity on We're Experiencing Technical Difficulties (Again) · · Score: 1

    so shoudl this be changed?

  5. Barebones Linux? Try NetBSD on Ask Slashdot: Creating a "Personal" Linux Distribution? · · Score: 1

    I was about to mention that one could take
    a barebones distribution of BSD as an
    example of what you need for a small
    distribution. Other examples would include
    going back and looking at the old MCC
    distributions. otherwise consider
    what tasks you need done:

    * a shell (sh compatible preferably)
    * shell utils (GNU)
    * fdisk
    * ext2 utils (mkfs, fsck)
    * editor (vi and/or emacs)
    * network utils (ifconfig, route, telnet, ping)
    * inetd/xinetd/etc
    * network server daemons (telnetd, samba, httpd,etc)
    * mail system (qmail, sendmail, postfix)
    * shared libraries (libc/glibc)
    * compiler/linker/assembler (gcc+binutils+.a's)
    * xwindows (xfree)

    that would be roughly what i would start
    with, and it shouldn't be that big.

  6. It was so their idea on FCC Decides ISP Calls are Long-Distance · · Score: 1


    *cough* you mean DARPA, the D (for defense)
    was later dropped to help public relations.
    Can't forget that the military was
    a big player in the development of the net.

  7. Somebody poop on your Stroopwaffles? on PIII - dead end technology? · · Score: 1

    the point is that one buys a cpu today to use against today's software. in two to three years the cpu market will be very different than today and the merced III and amd k9 will make the lil-ol' p-III look like a toy.

    besides, in three years, the 3d accel boards will offload everything anyhow ;)