We have a working landline phone/data network. Japan and Europe do not. Consumer demand for high-spec wireless kit has scaled appropriately in both areas.
(And yes, before I get piled on: I am well aware that you can get dial tone in Europe and Japan. You just can't get it quickly.)
I don't see what the fuss is all about, I patched my system when prompted to, I updated my Norton antivirus when prompted to, I've went on some websites which had the virus, It detected it, I've received e-mails with it, it detected it.
Unfortunatly, that approach only works if the antivirus update reaches your company before the virus reaches one of your dumber users.
NIMDA spread fast. There was a delay of almost 6 hours between the first infected host on our network and Sophos getting their ide file out to us.
Needless to say, the last few days haven't been fun.
I pay for DSL, i can run *WHATEVER* i want on it. Saying "tough beans" is a little short sighted.
That's a fascinating contention. But not, I suspect, one that would be substantiated by having a lawyer look over the contract you signed with your ISP.
Your signature on a legal document trumps your moral indignation. Next time, read the fine print.
Thank you. I was beginning to think that I was the only person here who still had a functioning long-term memory.
The linux world has just as much of a worm problem as the win32 world. Maybe even more: after all, your average installation of win2k or winME doesn't run IIS (or many net-listening daemons at all), whereas every official release of redhat ever made is trivially rootable out of the box in its default installation.
The lesson I learned the hard way from 1i0n: don't run sendmail. (Use postfix or qmail.) Don't run BIND. (Use djbdns or, um...something.) And whatever you do, never allow a "UUNet Certified Firewall Engineer" to configure and install your Checkpoint FW-1. And yes, virginia, there are such things as linux worms, and restoring 1,825 different index.html files from your backup tapes is a lousy way to spend a saturday afternoon.
"Faster and much less buggy than previous [mozilla] releases" is damning with faint praise, and only points out the extent to which they are still losing ground to IE.
0.9.4 on *nix still falls over and dies regularly when attempting to view sites with plugin (specifically, flash and real) content, nontrivial ECMAscript or complex table structures. It might be suitable for limited-purpose use (e.g. viewing internally designed web apps that you have personally vetted against mozilla), but it is still lightyears away from being an acceptable general-purpose web browser.
...what are the odds that the next version of CTOC will handle importing meeting requests sent from pure-Exchange sites to a CT/Exchange/CTOC site? And are we ever going to see an Entourage/Outlook-Mac version of the CTOC?
(Sorry, couldn't help it...it was just a little too obvious who you work for.:)
As a side note, I don't think I've ever been happier with the moderation on one of my posts here. "+4 Troll" is about exactly perfect for this one.
Re:Please don't link to bugzilla from the front pa
on
Chief Lizard Wrangler axed
·
· Score: 2, Flamebait
In the future, please think about the people who are relying on a particular server before targetting it for destruction.
Oh, they do think about it, trust me. In case you haven't noticed from the self-satisfied braying around here every time it happens (which is about five to ten times a day), "slashdotting" serves as a handy penis substitute for the hordes of socially malformed idiots that this place calls its audience...and its "editors."
This surprises me since BeOS itself on x86 was amazingly fast
Frankly, it shocked me as well. I remember playing around on a friend's BeBox back in 1996, and that damn thing was blisteringly fast on just a pair of 66mhz PPC 603s. I have to suspect that the bottleneck wasn't in the OS, but maybe in the video drivers or the like.
I would think you could put a surplus Pentium III (being given away in cereal boxes nowadays) and it would fly. My guess is that they must have cheaped out on the amount of memory they put in, which is pretty stupid considering how cheap 512MB modules are nowadays.
According to the Sony rep I was interrogating, the CPU was a 233MHz Cyrix chip, which can't have helped matters. Can't remember if it was 32 or 64MB of memory, but it certainly was constrained there in either case. Still, even so... given that the box really just wasn't doing that much, there wasn't any good excuse for the performance.
The whole thing had a very slapdash, still-in-beta feel to it. Which I guess was more or less the case.
I spent a good hour at the last PC-Expo here in new york city giving one of these things a thorough shakedown. You didn't miss anything.
It was slow as fuck. For all of BeOS/BeIA's vaunted performance, this thing was a turtle. The machine visibly chugged when redrawing large windows and switching between applications.
The only removable storage option were those damn Sony memory sticks. There were USB ports, but USB hard drives, zip drives and floppy drives were unsupported with no plans to ever add support.
There was some minimal support for opening up MS Word and Excel files (really, really minimal in Excel's case), but, astonishingly, no PDF support. Forget about flash/real/quicktime.
While the case was definitely pretty, everybody who described it as "like a Mac Classic" forgot to add "...only 50% wider and deeper, and 75% heavier."
The only good thing I can say about it is that it did successfully play mp3 playlists from my apache::mp3 server.
All in all, a pretty sad last stand for Jean-Louis Gassee's brilliant little OS. I'd be surprised if they sold even a hundred of these. If I ever see one for less than $75 on ubid or ebay, I might try to pick one up for sheer curiosity value, but I can't think of any other good reason to.
Though, I still think that a bash shell is best for a newbie, and Solaris 8 doesn't come with that.
Funny, every out-of-the-box installation of Sol/8 I've ever done had/bin/bash sitting right there. It's definitely on the CDs; what sort of oddball install are you doing?
zim# pkgchk -l -p/usr/bin/bash
Pathname:/usr/bin/bash
Type: regular file
Expected mode: 0555
Expected owner: root
Expected group: bin
Expected file size (bytes): 516392
Expected sum(1) of contents: 17782
Expected last modification: Jan 05 18:54:12 2000
Referenced by the following packages:
SUNWbash
Current status: installed
Sony hates Microsoft with a passion, they think their OS's are crap; not fit for human consumption. So, imagine a Sony Viao with a custom Sony OS(tm).
Gah. Sony may hate Windows. (Or they may not... they certainly make enough money on the Vaio line to make them happy.) But if you've ever tried to use any of Sony's own user-side software (the "Media Bar", DVgate, that damn thumbwheel thing), you should be very, very afraid of the idea of their engineers getting their grubby hands on the BeOS. Basically, these guys couldn't code their way out of a high-pressure weather system, nevermind a wet paper bag -- flushing 90% of the Sony-authored crap is the only way to make a Vaio usable.
I suspect that if this happened, this would become Sony's OS/2: half-heartedly promoted by one side of the company, while slowly ground into dust by the windows-using (and thus profit-making) arm of the company.
On the other hand, at least you can still buy OS/2, sorta. I guess anything's better than Chapter 7.
i read the fucking "manuals" what ever the fuck manuals are; search for google and you'll find lots of little write ups, some FAQ's some half baked guides, no "manual".
Chill, dude. I wasn't flaming you.
Anyways, the iptables(8) manpage will give you just about everything you need. Beyond that, try http://netfilter.samba.org/.
if redhat linux, or any linux for that matter is a product i would like them so state clealy on what the deal is with three competing firewalls shipping with their product.
Read what I wrote again. Linux 2.4.x comes with one and only one firewall: iptables. It is compatible with the old ipchains and ipfw user commands (for legacy support reasons), but that doesn't mean that those products are installed.
i really dislike the ipfw/ipchains/iptables crap. i would just like to be presented with one that is the standard.
Reading the Fine Manuals might have cleared up your confusion on that score...
In any case, here's the short answer: iptables is the standard on 2.4.x and henceforth. Period, end of discussion. The ipchains/ipfw user and api interfaces are provided for the usual legacy support reasons, but the iptables code is still doing the lifting.
Ugly, but you can only change so many things before the major distribution vendors start sending you dead squirrels by surface post in appreciation for making their lives more difficult.
As a user, you can download it, you can hack the source, you can use it. You simply cannot distribute changes to the source. This is essentially the same terms as DJB software packages such as qmail, djbdns, and publicfile.
This is not entirely correct. You can distribute changes to the source for pine/djb-licensed software. (There's tons and tons of patches for qmail on www.qmail.org.) All that you can't do is distribute a tarball of the source with your changes already applied, or a binary package built from your changed sources. Aggravating, but not exactly the end of the world.
Computers are commodities, and Apple's attempt to decommoditize their systems by making them "unique" in some way just isn't going to work for the masses.
Yeah, everybody knows you can't make any money doing that. Just look at how BMW, Mercedes and Jaguar all atopped making cars years ago. Oh wait, they didn't.
If they're content with selling to the ever-dwindling Mac-loving $80k income crowd, that's fine; they should then abandon all hope of reaching the rest of us who want the best computing for the lowest cost.
Apple abandoned (or was abandoned by, your call) the most-MIPS-for-fewest-dollars crowd damn close to a decade ago. They are targeting a market for whom "best computing" is measured by a few things other than MHz, and by and large they've managed to keep turning a profit at it.
Cheap, reliable, compatible
...pick two.
AMD chips, ABIT motherboards, brand X RAM, WD IDE hard drives.
Excuse me? You're trying to spec out a machine that is both cheap and reliable and you're recommending a VIA chipset, no-name RAM and a Western-Digital hard drive?
This same elitist streak in Apple led to the 'innovation' of their sleek, gorgeous one-button mouse.
Sigh. This again. One day an Apple-topic story will be posted on/. without the "one-button-mouse" troll being sounded, and then the world will promptly end.
One more time, with feeling then: Apple's choice of a one-button mouse had nothing to do with any alleged "artistically elitist" inclination, but was a conscious, deliberate choice based on thousands and thousands of hours of actual usability testing. You can second-guess the decision as much as you like in hindsight, but the cold hard fact is that they made it only after actually assessing the data.
Now I can't guarantee that Carlton's book is an objective and unbiased account of the times.
If it's written with the same loving care and attention to details that his online columns are, I wouldn't trust it to correctly report the color of the sky over Apple's headquarters on any given day.
That said, he probably has the rough facts right about Apple's abortive next-gen OS projects. Enough of that ongoing debacle played out in public that even a hack like Carlton couldn't help but stumble over a few of the facts.
Occasionally I like to amuse myself by trying to list all of them from memory. Let's try, shall we?
MacMach (CMU's Mach microkernel with OS7 hosted on it as a mach server...also hauntingly familiar, eh?)
StarTrek (OS7-on-Intel. A finished project: the OS booted and ran recompiled apps on a Pentium-66 faster than any machine Apple had ever shipped at the time. Killed and buried when Apple drank IBM's kool aid and commited to the PowerPC.)
Pink (far-out network-centric, object-oriented distributed OS that Apple had working in the labs as far back as 1992. Later turned into:
Taligent (Pink plus IBM's patented "OS/2 Kiss of Death" technology)
AIX (apple actually shipped boxes running AIX 4.1.3. as an amusing side-effect, you could actually boot OS8 on certain IBM RS/6000 servers)
NetWare for PowerMac. (Novell demonstrated this one at two consecutive MacWorlds, but never shipped it.)
MkLinux (Linux userland server hosted on our old buddy Mach...still kicking around on a few 1st-generation PowerMacs)
Copland -- you might have heard about this one. Started out as just OS7 plus protected memory...ended up with a proposed feature list a mile long and a ship date always a mile away.
Gershwin -- allegedly the full-on rock-em-sock-em retooled-from-the-ground-up followup to Copland
Rhapsody (AKA "NeXTStep 5.0 on PowerPC with OS8 window manager widgets...we're sure nobody will notice the difference!")
...and those are just the ones I can remember off the top of my head, and I'm not even counting the Newton OS or any of their other weird side-projects. (For instance, I'd give my eyeteeth to know what kind of OS the prototyped Apple set-top boxes that popped up on ebay last year were meant to run...)
Given that history, I am still stunned that OS X actually shipped.
How long do you think the big media conglomerates would put up with shit like that?
Unfortunatly, the answer to that is "as long as they're making money off of it, potentially indefinitely." CNN, Gannett, and most of the major newswires already produce asian-market localizations which are trimmed to protect the sensibilities of various authoritarian states, primarily China and Singapore.
The Chinese government figured this out years ago: as long as they let the roundeyes come in and sell their goods to what amounts to the last major unexploited market, the foreign barbarians will happily pay the bribes, accept the arbitrary censorship, and pay lip service to their alleged democratic ideals while crying all the way to the bank.
Folks, this is a pure corporate power play of the highest order.
The context for this action is very simple: The RBOCs want the CLECs and DSL-LECs dead. They've been working diligently towards that goal since they appeared, and this is the end-game move against one of the largest.
DSL was a genie that the Baby Bells uncorked back in the mid-90s when it looked like Voice-over-IP on cable modems was going to spontaneously eat their lunch. Now that they've pretty successfully bought the necessary legislation to prevent the cablecos from offering Voice service in most areas, they are desperately trying to stuff the genie back in the bottle, in order to preserve their enormous profit margins on (decades-old) DS1 and frame relay technologies.
Northpoint and Rhythms cheerfully took themselves out of the game, so Covad is the last target, and Covad has a huge groundswell of consumer sympathy on their side, due to just the sort of routine horror stories that are on display in the comments above. And that outcry is beginning to develop into interest at the regulatory and legislative levels: a very bad scenario from Verizon's perspective.
So what we have here is a pre-emptive strike against any possible Congressional inquiry into Verizon's practices vis a vis the DSL-LECs. Covad's going to complain that Verizon's sabotaging their installs? Quick, find some disgruntled ex-employees (there's been a few rounds of layoffs, shouldn't be too hard) who'll swear that the complaints are bogus. Doesn't really matter if they're telling the truth or not; hell, by the time the discovery phase of the case is over, Covad might be out of business. The whole point is to make the case exist at all, to muddy the waters enough to deter any possible inquiry from Congress or the states' attorneys general.
And it'll probably work. Oh well, my $200 SDSL was nice while it lasted.
Bind 9.0 is safer because it was written from scratch with security in mind, unlike the prior versions.
No, it is not.
I completely understand why RedHat's corporate policy vis a vis open source software (nevermind the debacle of your original attempt to evaluate qmail for inclusion in 6.0)prevents you from including djb's software in your distribution, but let's not pretend for a moment that BIND 9 is any improvement. Please, throw money and engineers at DENTS or one of the other open-source name server projects.
Slashdot Mirror
We have a working landline phone/data network. Japan and Europe do not. Consumer demand for high-spec wireless kit has scaled appropriately in both areas.
(And yes, before I get piled on: I am well aware that you can get dial tone in Europe and Japan. You just can't get it quickly.)
I don't see what the fuss is all about, I patched my system when prompted to, I updated my Norton antivirus when prompted to, I've went on some websites which had the virus, It detected it, I've received e-mails with it, it detected it.
Unfortunatly, that approach only works if the antivirus update reaches your company before the virus reaches one of your dumber users.
NIMDA spread fast. There was a delay of almost 6 hours between the first infected host on our network and Sophos getting their ide file out to us.
Needless to say, the last few days haven't been fun.
I pay for DSL, i can run *WHATEVER* i want on it. Saying "tough beans" is a little short sighted.
That's a fascinating contention. But not, I suspect, one that would be substantiated by having a lawyer look over the contract you signed with your ISP.
Your signature on a legal document trumps your moral indignation. Next time, read the fine print.
Hello? Ramen? 1i0n? Adore? Sound familiar?
Thank you. I was beginning to think that I was the only person here who still had a functioning long-term memory.
The linux world has just as much of a worm problem as the win32 world. Maybe even more: after all, your average installation of win2k or winME doesn't run IIS (or many net-listening daemons at all), whereas every official release of redhat ever made is trivially rootable out of the box in its default installation.
The lesson I learned the hard way from 1i0n: don't run sendmail. (Use postfix or qmail.) Don't run BIND. (Use djbdns or, um...something.) And whatever you do, never allow a "UUNet Certified Firewall Engineer" to configure and install your Checkpoint FW-1. And yes, virginia, there are such things as linux worms, and restoring 1,825 different index.html files from your backup tapes is a lousy way to spend a saturday afternoon.
"Faster and much less buggy than previous [mozilla] releases" is damning with faint praise, and only points out the extent to which they are still losing ground to IE.
0.9.4 on *nix still falls over and dies regularly when attempting to view sites with plugin (specifically, flash and real) content, nontrivial ECMAscript or complex table structures. It might be suitable for limited-purpose use (e.g. viewing internally designed web apps that you have personally vetted against mozilla), but it is still lightyears away from being an acceptable general-purpose web browser.
If you want to discuss this further, maybe we should do this via e-mail, since this is getting out of context
Happy to. memory-ctoc@tunameltdown.com. (I'd write you, but you have no address available.)
...what are the odds that the next version of CTOC will handle importing meeting requests sent from pure-Exchange sites to a CT/Exchange/CTOC site? And are we ever going to see an Entourage/Outlook-Mac version of the CTOC?
:)
(Sorry, couldn't help it...it was just a little too obvious who you work for.
Does anyone else find this post a little ironic?
Well, I would certainly hope so.
As a side note, I don't think I've ever been happier with the moderation on one of my posts here. "+4 Troll" is about exactly perfect for this one.
In the future, please think about the people who are relying on a particular server before targetting it for destruction.
Oh, they do think about it, trust me. In case you haven't noticed from the self-satisfied braying around here every time it happens (which is about five to ten times a day), "slashdotting" serves as a handy penis substitute for the hordes of socially malformed idiots that this place calls its audience...and its "editors."
Frankly, it shocked me as well. I remember playing around on a friend's BeBox back in 1996, and that damn thing was blisteringly fast on just a pair of 66mhz PPC 603s. I have to suspect that the bottleneck wasn't in the OS, but maybe in the video drivers or the like.
I would think you could put a surplus Pentium III (being given away in cereal boxes nowadays) and it would fly. My guess is that they must have cheaped out on the amount of memory they put in, which is pretty stupid considering how cheap 512MB modules are nowadays.
According to the Sony rep I was interrogating, the CPU was a 233MHz Cyrix chip, which can't have helped matters. Can't remember if it was 32 or 64MB of memory, but it certainly was constrained there in either case. Still, even so... given that the box really just wasn't doing that much, there wasn't any good excuse for the performance.
The whole thing had a very slapdash, still-in-beta feel to it. Which I guess was more or less the case.
All in all, a pretty sad last stand for Jean-Louis Gassee's brilliant little OS. I'd be surprised if they sold even a hundred of these. If I ever see one for less than $75 on ubid or ebay, I might try to pick one up for sheer curiosity value, but I can't think of any other good reason to.
You have no soul. Can I interest you in a slightly used one, at a great price?
Funny, every out-of-the-box installation of Sol/8 I've ever done had /bin/bash sitting right there. It's definitely on the CDs; what sort of oddball install are you doing?
zim# pkgchk -l -p /usr/bin/bash /usr/bin/bash
Pathname:
Type: regular file
Expected mode: 0555
Expected owner: root
Expected group: bin
Expected file size (bytes): 516392
Expected sum(1) of contents: 17782
Expected last modification: Jan 05 18:54:12 2000
Referenced by the following packages:
SUNWbash
Current status: installed
Gah. Sony may hate Windows. (Or they may not... they certainly make enough money on the Vaio line to make them happy.) But if you've ever tried to use any of Sony's own user-side software (the "Media Bar", DVgate, that damn thumbwheel thing), you should be very, very afraid of the idea of their engineers getting their grubby hands on the BeOS. Basically, these guys couldn't code their way out of a high-pressure weather system, nevermind a wet paper bag -- flushing 90% of the Sony-authored crap is the only way to make a Vaio usable.
I suspect that if this happened, this would become Sony's OS/2: half-heartedly promoted by one side of the company, while slowly ground into dust by the windows-using (and thus profit-making) arm of the company.
On the other hand, at least you can still buy OS/2, sorta. I guess anything's better than Chapter 7.
Because I answered the question. Correctly, even.
i read the fucking "manuals" what ever the fuck manuals are; search for google and you'll find lots of little write ups, some FAQ's some half baked guides, no "manual".
Chill, dude. I wasn't flaming you.
Anyways, the iptables(8) manpage will give you just about everything you need. Beyond that, try http://netfilter.samba.org/.
if redhat linux, or any linux for that matter is a product i would like them so state clealy on what the deal is with three competing firewalls shipping with their product.
Read what I wrote again. Linux 2.4.x comes with one and only one firewall: iptables. It is compatible with the old ipchains and ipfw user commands (for legacy support reasons), but that doesn't mean that those products are installed.
Reading the Fine Manuals might have cleared up your confusion on that score...
In any case, here's the short answer: iptables is the standard on 2.4.x and henceforth. Period, end of discussion. The ipchains/ipfw user and api interfaces are provided for the usual legacy support reasons, but the iptables code is still doing the lifting.
Ugly, but you can only change so many things before the major distribution vendors start sending you dead squirrels by surface post in appreciation for making their lives more difficult.
This is not entirely correct. You can distribute changes to the source for pine/djb-licensed software. (There's tons and tons of patches for qmail on www.qmail.org.) All that you can't do is distribute a tarball of the source with your changes already applied, or a binary package built from your changed sources. Aggravating, but not exactly the end of the world.
Yeah, everybody knows you can't make any money doing that. Just look at how BMW, Mercedes and Jaguar all atopped making cars years ago. Oh wait, they didn't.
If they're content with selling to the ever-dwindling Mac-loving $80k income crowd, that's fine; they should then abandon all hope of reaching the rest of us who want the best computing for the lowest cost.
Apple abandoned (or was abandoned by, your call) the most-MIPS-for-fewest-dollars crowd damn close to a decade ago. They are targeting a market for whom "best computing" is measured by a few things other than MHz, and by and large they've managed to keep turning a profit at it.
Cheap, reliable, compatible
AMD chips, ABIT motherboards, brand X RAM, WD IDE hard drives.
Excuse me? You're trying to spec out a machine that is both cheap and reliable and you're recommending a VIA chipset, no-name RAM and a Western-Digital hard drive?
<daffy duck voice>
HaheehahoohooHaheehahoohooHaheehahoohooHaheehahooh oo
</daffy duck voice>
Rotsa ruck, man.
Sigh. This again. One day an Apple-topic story will be posted on /. without the "one-button-mouse" troll being sounded, and then the world will promptly end.
One more time, with feeling then: Apple's choice of a one-button mouse had nothing to do with any alleged "artistically elitist" inclination, but was a conscious, deliberate choice based on thousands and thousands of hours of actual usability testing. You can second-guess the decision as much as you like in hindsight, but the cold hard fact is that they made it only after actually assessing the data.
If it's written with the same loving care and attention to details that his online columns are, I wouldn't trust it to correctly report the color of the sky over Apple's headquarters on any given day.
That said, he probably has the rough facts right about Apple's abortive next-gen OS projects. Enough of that ongoing debacle played out in public that even a hack like Carlton couldn't help but stumble over a few of the facts.
Occasionally I like to amuse myself by trying to list all of them from memory. Let's try, shall we?
Given that history, I am still stunned that OS X actually shipped.
Unfortunatly, the answer to that is "as long as they're making money off of it, potentially indefinitely." CNN, Gannett, and most of the major newswires already produce asian-market localizations which are trimmed to protect the sensibilities of various authoritarian states, primarily China and Singapore.
The Chinese government figured this out years ago: as long as they let the roundeyes come in and sell their goods to what amounts to the last major unexploited market, the foreign barbarians will happily pay the bribes, accept the arbitrary censorship, and pay lip service to their alleged democratic ideals while crying all the way to the bank.
Yeah, god knows nobody's ever done that here before.
Nope, all in all I think flaming you might actually be more fun. And more useful to the human race. Idiot.
Axiomatically, everything in your post from "but..." onwards is comprised of idiotic redundancies.
Don't you have anything useful to do?
The context for this action is very simple: The RBOCs want the CLECs and DSL-LECs dead. They've been working diligently towards that goal since they appeared, and this is the end-game move against one of the largest.
DSL was a genie that the Baby Bells uncorked back in the mid-90s when it looked like Voice-over-IP on cable modems was going to spontaneously eat their lunch. Now that they've pretty successfully bought the necessary legislation to prevent the cablecos from offering Voice service in most areas, they are desperately trying to stuff the genie back in the bottle, in order to preserve their enormous profit margins on (decades-old) DS1 and frame relay technologies.
Northpoint and Rhythms cheerfully took themselves out of the game, so Covad is the last target, and Covad has a huge groundswell of consumer sympathy on their side, due to just the sort of routine horror stories that are on display in the comments above. And that outcry is beginning to develop into interest at the regulatory and legislative levels: a very bad scenario from Verizon's perspective.
So what we have here is a pre-emptive strike against any possible Congressional inquiry into Verizon's practices vis a vis the DSL-LECs. Covad's going to complain that Verizon's sabotaging their installs? Quick, find some disgruntled ex-employees (there's been a few rounds of layoffs, shouldn't be too hard) who'll swear that the complaints are bogus. Doesn't really matter if they're telling the truth or not; hell, by the time the discovery phase of the case is over, Covad might be out of business. The whole point is to make the case exist at all, to muddy the waters enough to deter any possible inquiry from Congress or the states' attorneys general.
And it'll probably work. Oh well, my $200 SDSL was nice while it lasted.
Bind 9.0 is safer because it was written from scratch with security in mind, unlike the prior versions. No, it is not. I completely understand why RedHat's corporate policy vis a vis open source software (nevermind the debacle of your original attempt to evaluate qmail for inclusion in 6.0)prevents you from including djb's software in your distribution, but let's not pretend for a moment that BIND 9 is any improvement. Please, throw money and engineers at DENTS or one of the other open-source name server projects.