I downloaded these last week, I think somebody around here had pointed them out.
There is something extremely peaceful and soothing to these songs. I looped them back-to-back for an hour or so, and I swear it was among the most transcendant experiences I've had this year.
They also have a distinct 20th century edginess to them; whoever arranged these had quite the mastery of rhythm.;-)
Well put. If it were a web server that I had installed for a client, right now I'd be furiously scrambling to fix it...
The Cisco 675 I'm using for the connection is actually fairly robust in terms of routing capabilities, despite it's deceptively small size. So far, so good, at least.;-)
Thanks for the tip about SSLftp. It sounds like just what I've been looking for.
P.S. Doesn't the BSD section of slash seem peaceful today? I swear, I should just delete my bookmark of the front page and come here direct.
Thanks for the advice, I just took a wild stab at the mod; it's my box, so although I won't be thrilled if it starts to bug out, I won't be especially heartbroken either.;-)
It seems to be working fine so far; $ uptime 12:10AM up 2 days, 13:06, 1 user, load averages: 0.08, 0.08, 0.08 $ and it would be longer except I upgraded to OpenBSD 2.7 when it came out last Thursday. If the fan/PS are still running, can I assume that the resistor/fan mod is working OK? Or is it dangerous to run for extended periods of time?
What kind of resistor would work best for a resistor in series here, for a 12V fan? I know you probably can't tell me exactly, but a ballpark range (watts/ohms) would probably help me (and others) out. Are there any good practical sites you know of that have very simple electronics lessons? I'd love to learn more about this stuff, it always interested me.
In terms of air flow, it seems to be getting enough flow out the back of the case; the temperature of the air is cool, so if it was overheating I'd probably be able to tell by now.
I just built a server last week, and one of my goals was to make it somehow quieter than it had been. It was built from an old Compaq Deskpro a client had given up on, and when I got it, it sounded like a fricking airport. I record music with my computer, so keeping the volume level down has assumed some importance, especially since I have three or four computers going sometimes. Microphones are pretty sensitive these days, and digital recordings only serve to expose any extraneous noise in the environment, while analog tapes sometimes help to mask such artifacts.
Anyway, moving right along. I basically had taken the Compaq Deskpro apart, stripping it for parts, even took out the processor and the hard drives and cables, even the proprietary BIOS (which I subsequently had to hunt up of course.)
I had pretty much stripped the thing, short of taking out the motherboard, and chucked it in my basement for around 8 months until I remembered it.
When I rebuilt it, it took a while to find all the pieces, but I finally got it back together. Everything worked fine; I noticed it was a P-133 (not MMX) with a fairly decent heatsink on it. What the hell could be making that much noise??? It sounded like a wheezing tuberculosis patient.
So I snooped around a bit, and looked at it from a few angles, and lo and behold, it was of course the power supply fan. "Aha!" I thought to myself. "I'll just replace the fan with another, quieter fan!"
So after trying about four equally noisy fans (and lord only knows why they sounded like jet airplanes) it occurred to me that perhaps they were receiving too much current.
I'm no electronics expert, but I seemed to remember something about resistors (those funky little striped electronic thingers) resisting current, so I hunted up my box of spare parts, and tried throwing a couple of 'em on in series with the power supply fan.
Eventually I found one that was just right, and it slowed the fan down to that perfect balance, between putting out enough air current, and sounding like the Los Alamos Wind Turbine Hurricane Emulator.
I guess what I'm saying is; if you have an especially loud fan in your computer, why not just step the current down a little bit? Sure, it might not blow out quite as much air as it did, but you won't find yourself trying to figure out where that whooshing sound is coming from, either.
Probably won't work if your machine is overclocked though...;-) In that case, get a Peltier instead. Or earplugs.
My Hotmail account works just fine, no missing emails, address book, or whatnot.
And, do you mean to tell me you haven't backed that stuff up anyway? What, you actually trust Microsoft to do something right? Sheesh. Newbie.;-)
Anyway, I like Hotmail; I like being able to check my email from anywhere I can find an internet connection. The longest downtime I've had was 12-14 hours once. They've lost and restored my messages (all of them) twice. They are notorious for locking people out of accounts that are too large. They obviously have some problems with spam. If they ever try to move their backend servers to NT again, I will probably be screwed.
That said, I like Hotmail. They pioneered free webmail, and they remain one of the better free webmail services out there. That doesn't mean you should trust them. It's fricking Microsoft we're talking about here.
Indeed, Samba is inherently vulnerable to the same types of attacks as other file servers, including ftp and nfs. In fact, ftpd is even more vulnerable to attack than Samba is, because ftp passes network passwords in plaintext! Any bozo with a sniffer on your LAN, router, or subnet can snare passwords right out of an ftp logon. On the other hand, Samba can be set to use encrypted passwords, which is not 100% secure, but much better than plaintext.
That, coupled with the fact that I've taken the liberty of creating user accounts on the OpenBSD box specifically to access Samba shares, (which have very few other privileges) makes me more worried about the physical security (i.e. theft, tornado, etc) of this particular box than I am about 'leet hax0rs right now.
I'm not saying this is an ideal setup, but Samba is very useful to have in a shop with multiple clients running Windows NT, 98, MacOS, and Linux. The Samba team has actually done rather well at making it fairly (not totally, as you pointed out) secure, too. They have features that can limit access to files by IP, user-level security, and file-level security.
In theory, you're right; a web server would have no other services running, for maximum security. In this case, it's impractical to buy yet another dedicated server, just for file serving. Most small shops like mine can't afford multiple physical servers, and it's becoming pretty commonplace to see a web server doing double or even triple duty as file servers or proxies. I'm not saying it's a good thing, it's just the way it is.
Here's some food for thought, though; if you had to support a large client base of Winboxen, would you rather be running NT server, or OpenBSD with Samba? I know which one I chose. In fact, we're in the process of migrating most of our services (DNS, Proxy, etc) from NT and even Linux boxes to OpenBSD, purely because of the security and stability.
Nethack, on the other hand, I can't justify. But then again, I don't need to, being the admin and all.;-)
BTW, I heard a rumour there is a more secure form of FTP available, that uses RSA or DSA encryption. Anyone know what that is?
Let's see; if OpenBSD can guarantee security, guarantee availability, and (hopefully) integrate the RTMX code base, without disrupting the inherent stability, won't that start to give companies like QNX a run for their money?
I am afraid to admit I don't know much about RTMX; has anyone used it before? How important is guaranteed availability to most applications? Is anyone reading this using RTMX for mission critical apps?
BTW, I'm running the new OpenBSD 2.7 release at my web site, and it's been fantastic. It's running Apache with SSL, Samba for file and printer sharing, and Nethack for when I get bored. The install took about 1.5 hours.
All right, I'll not try and convince you again. You've made a choice, and you're sticking to it.
;-)
I get some mail from Theo (not to me personally, to the lists), and, although I'm not sure how long it will last, he is generally civil and forthcoming in them...
I don't know what to say about the packet filtering; is FreeBSD still filtering out packets from the OpenBSD networks, as they claim? "We won't stop filtering packets from the OpenBSD networks until Theo is out". Heh, it's fun to read archived threads sometimes.
Well, thanks for being honest; it's important for me to know how OpenBSD got its reputation. You seem like a good person, with very valid reasons for not using OpenBSD.
I can respect that; there are many people who agree with you.
However, it's interesting to notice some people will pay good money for excellent software, even without being able to try it out first. If you're resourceful, you can even get OpenBSD for (close to) free, as you pointed out.
Some people find Theo's development style and anti-social behavior to be abrasive, but since when have those qualities stopped anyone from being a fantastic software developer? Consider Picasso for a moment; although you may find him intensely disagreeable as a person, does that mean you will never find meaning in his paintings?
I urge you to reconsider OpenBSD, if you are holding back simply because of Theo's personality. OpenBSD is a truly refined, unusual experience, and, trust me on this; you can enjoy the meal without liking the chef.
I agree; I'm still forced to use Windows98 to some degree (don't ask), but I have free reign as far as determining my (and my clients) server OS's.
OpenBSD is fantastic for servers, especially if you don't need to run KDE or Gnome apps (although, I'm sure you could figure out how to run some o' them new-fangled window managers, if you are so inclined.) If you are looking for a desktop system, though, I'd look elsewhere. Personally I don't even install X11 if I can help it.
The encrypted swap feature is not one of the points that initially sold me on OpenBSD (although it does sound über-sexy at cocktail parties). =P
It's the other, shall I say, more practical (OK, all right, probably more boring, too; but...) features that I like. Like SSH built-in, and everything locked down by default. Not necessarily cutting-edge, but nice. I sleep well at night.
Well said. You seem to understand exactly how much benefit will come from having an awesome and intuitive GUI, evolved from a combination of the world's most popular GUI's and an awesome core OS.
You know, I agree with that. You really don't need to be running things as powerful as Bind.
Unfortunately, the default installations of many Linux distros seem to be getting more and more top-heavy. Even things like Bind and Sendmail are getting installed by default; I'm not sure if this is a good thing.
One thing I like about OpenBSD is the very sparse, almost Bauhaus-style install. You have to go through manually and set things up if you want to use them.
It seems like a lot of work, and it perhaps is very cumbersome if you've never done it before, but I just feel much more comfortable running an OS that doesn't have a whole bunch of crufty packages installed that I may or may not ever want or need.
The security audit for OpenBSD helps, too, though.;-)
Re:bsd succumbing to the latest fad
on
Java 2 For BSD
·
· Score: 1
I would, of course, never intentionally make an inflammatory statement. =P
I played a decker for a while in my (albeit somewhat short-lived) Shadowrun career. It was pretty cool to realize that the possibility of having a data port (I hope it's not 10/100!) built into your skull was getting closer to life.
Shadowrun would be the ideal starting point for a MMRP. If people could get behind the Worldforge project, and use the Shadowrun series of books for the code base (being careful to not make the universes too close together, for obvious copyright reasons), it just might be the sort of project that would snowball into something wicked.
The real question is, will the Open Source model work for a large gaming project? Or is the budget constraint just too huge in comparison to the $oftware companie$?
Anyway, I'd love to see the Shadowrun universe online, in an immersive RPG.
Stupid article though.
Re:bsd succumbing to the latest fad
on
Java 2 For BSD
·
· Score: 1
Heh, no, I agree that only suX0rs use Java on their desktops, unless they are masochistic or insane or forced to for some reason. =P
However, a lot of companies are using Java for middleware and server-based applets (servlets).
I agree that the BSD's should think carefully before jumping in to every technology that happens along, but Java is already become entrenched in the enterprise. If a Java port comes out, that doesn't mean you suddenly *have* to install it on your BSD boxen.
I guess I just find it disturbing that the original poster was able to get away with posting such FUD, like "I trained in Java in the war of 1967", and "recent studies indicate that Java != bad coffee". If you don't like Java or BSD, fine. But don't post a bunch of crap just trying make a given technology look bad.
Re:bsd succumbing to the latest fad
on
Java 2 For BSD
·
· Score: 1
That's interesting. Can you back up your statements with any links to the studies, etc? I'd be very interested in the Sun study in particular.
I was under the impression that Java, though initially it failed to live up to the cross-platform promises, was now running fairly well, with (mostly) portable code and a faster compile time, more standardization, etc.
Is it really that bad? Or are you just trying to get over a bad initial experience with Java?
As for seperate code bases maintained by seperate teams, that may indeed be one good way to develop, but I'm not sure if every project requires that much redundancy of effort.
Indeed, if they can port this to OpenBSD it will bode well for the existence of *BSD's in the enterprise. OpenBSD is one of the most stable, secure, and stress-tested OS's around. If it can run Java code, it would probably make one of the better choices for middleware and ASP's. I'm excited for the other BSD's to run it as well, of course, but I'm particularly excited about the possibility of an OpenBSD port because of its development history.
Quality of service contracts are going to be the make-or-break deciding factor for ASP's. OpenBSD can provide the uptime an applications provider will need to meet that contract; it's been through a year and a half security audit (which happened to close many software bugs as a side benefit), and uptimes in the hundreds of days are common.
OpenBSD 2.7 comes out next week, with integrated SSH2 and a large collection of packages and ports!
Disclaimer: I'm not affiliated with OpenBSD. I use it though =P
How could I have overlooked what sounds like a pretty cool show?
Seriously, never heard of the Iron Chef before...anybody got any *working* links to any fan sites? I'd like to see what its all about.
I don't have cable....hmmm....maybe that's why. Guess I should refrain on commenting about the "Rights" aspect, since I have no idea what the show is about.;-)
What portions of his post did you find to be the most descriptive? Was it the part where he said he thought they must have improved the graphical installation of the package selection parts? Or was it some other part in particular?
BSD hasn't "lost". (Even if they have, do you really want to be standing in the "Winner's Circle" with Bill Gates? Do you really want to have NT/Win2K on your "Killer Resume"?)
Most people don't need the reliability/security/speed of a BSD these days. Those that do, well, we seek them out. That's why market share for the BSDs is slipping; not because there aren't more BSD machines coming online, but because there are far more user machines (i.e. not bulletproof OpenBSD servers) proportionally coming online.
Believe me, when some of the larger sites out there start to find out that NT sucks harder than a Studebaker vacuum cleaner, and that Linux isn't the answer to everything (yeah yeah mod me down), there will be *many* conversions to BSD. Until then, market share will suffer as Linux continues to get the hype, NT continues to get the $ale$, and BSD continues to get overlooked.
The BSD's are a niche operating system. They are never going to have the mass appeal of a Windows GUI or a Windows GUI ripoff (KDE?), but that's OK; they don't need to. The BSDs attract people who are serious about building clean, stable, robust systems. They don't need to attract a large market share; the people who run BSD systems already aren't going to abandon them for Red Hat or NT anytime soon. Remember when Hotmail tried to move to NT?
It only took me about 6 months to figure out that I wanted to run OpenBSD on most of my servers. It might take other people longer, but they'll figure it out.
Oh, and I'd forget about a BSD "Summit" anytime soon; the grudges that caused the NetBSD/OpenBSD rift still sting a little too much.
Slashdot Mirror
There is something extremely peaceful and soothing to these songs. I looped them back-to-back for an hour or so, and I swear it was among the most transcendant experiences I've had this year.
They also have a distinct 20th century edginess to them; whoever arranged these had quite the mastery of rhythm. ;-)
The Cisco 675 I'm using for the connection is actually fairly robust in terms of routing capabilities, despite it's deceptively small size. So far, so good, at least. ;-)
Thanks for the tip about SSLftp. It sounds like just what I've been looking for.
P.S. Doesn't the BSD section of slash seem peaceful today? I swear, I should just delete my bookmark of the front page and come here direct.
It seems to be working fine so far; $ uptime 12:10AM up 2 days, 13:06, 1 user, load averages: 0.08, 0.08, 0.08 $ and it would be longer except I upgraded to OpenBSD 2.7 when it came out last Thursday. If the fan/PS are still running, can I assume that the resistor/fan mod is working OK? Or is it dangerous to run for extended periods of time?
What kind of resistor would work best for a resistor in series here, for a 12V fan? I know you probably can't tell me exactly, but a ballpark range (watts/ohms) would probably help me (and others) out. Are there any good practical sites you know of that have very simple electronics lessons? I'd love to learn more about this stuff, it always interested me.
In terms of air flow, it seems to be getting enough flow out the back of the case; the temperature of the air is cool, so if it was overheating I'd probably be able to tell by now.
Anyway, moving right along. I basically had taken the Compaq Deskpro apart, stripping it for parts, even took out the processor and the hard drives and cables, even the proprietary BIOS (which I subsequently had to hunt up of course.)
I had pretty much stripped the thing, short of taking out the motherboard, and chucked it in my basement for around 8 months until I remembered it.
When I rebuilt it, it took a while to find all the pieces, but I finally got it back together. Everything worked fine; I noticed it was a P-133 (not MMX) with a fairly decent heatsink on it. What the hell could be making that much noise??? It sounded like a wheezing tuberculosis patient.
So I snooped around a bit, and looked at it from a few angles, and lo and behold, it was of course the power supply fan. "Aha!" I thought to myself. "I'll just replace the fan with another, quieter fan!"
So after trying about four equally noisy fans (and lord only knows why they sounded like jet airplanes) it occurred to me that perhaps they were receiving too much current.
I'm no electronics expert, but I seemed to remember something about resistors (those funky little striped electronic thingers) resisting current, so I hunted up my box of spare parts, and tried throwing a couple of 'em on in series with the power supply fan.
Eventually I found one that was just right, and it slowed the fan down to that perfect balance, between putting out enough air current, and sounding like the Los Alamos Wind Turbine Hurricane Emulator.
I guess what I'm saying is; if you have an especially loud fan in your computer, why not just step the current down a little bit? Sure, it might not blow out quite as much air as it did, but you won't find yourself trying to figure out where that whooshing sound is coming from, either.
Probably won't work if your machine is overclocked though... ;-) In that case, get a Peltier instead. Or earplugs.
And, do you mean to tell me you haven't backed that stuff up anyway? What, you actually trust Microsoft to do something right? Sheesh. Newbie. ;-)
Anyway, I like Hotmail; I like being able to check my email from anywhere I can find an internet connection. The longest downtime I've had was 12-14 hours once. They've lost and restored my messages (all of them) twice. They are notorious for locking people out of accounts that are too large. They obviously have some problems with spam. If they ever try to move their backend servers to NT again, I will probably be screwed.
That said, I like Hotmail. They pioneered free webmail, and they remain one of the better free webmail services out there. That doesn't mean you should trust them. It's fricking Microsoft we're talking about here.
Ever look at the XML output of Office 2000? Well, I have, and Microsoft has once again pissed openly in the standards river.
It is the ugliest, most proprietary excuse for standards compliance that I have ever fricking seen. Embrace and extend this!
That, coupled with the fact that I've taken the liberty of creating user accounts on the OpenBSD box specifically to access Samba shares, (which have very few other privileges) makes me more worried about the physical security (i.e. theft, tornado, etc) of this particular box than I am about 'leet hax0rs right now.
I'm not saying this is an ideal setup, but Samba is very useful to have in a shop with multiple clients running Windows NT, 98, MacOS, and Linux. The Samba team has actually done rather well at making it fairly (not totally, as you pointed out) secure, too. They have features that can limit access to files by IP, user-level security, and file-level security.
In theory, you're right; a web server would have no other services running, for maximum security. In this case, it's impractical to buy yet another dedicated server, just for file serving. Most small shops like mine can't afford multiple physical servers, and it's becoming pretty commonplace to see a web server doing double or even triple duty as file servers or proxies. I'm not saying it's a good thing, it's just the way it is.
Here's some food for thought, though; if you had to support a large client base of Winboxen, would you rather be running NT server, or OpenBSD with Samba? I know which one I chose. In fact, we're in the process of migrating most of our services (DNS, Proxy, etc) from NT and even Linux boxes to OpenBSD, purely because of the security and stability.
Nethack, on the other hand, I can't justify. But then again, I don't need to, being the admin and all. ;-)
BTW, I heard a rumour there is a more secure form of FTP available, that uses RSA or DSA encryption. Anyone know what that is?
I am afraid to admit I don't know much about RTMX; has anyone used it before? How important is guaranteed availability to most applications? Is anyone reading this using RTMX for mission critical apps?
BTW, I'm running the new OpenBSD 2.7 release at my web site, and it's been fantastic. It's running Apache with SSL, Samba for file and printer sharing, and Nethack for when I get bored. The install took about 1.5 hours.
I get some mail from Theo (not to me personally, to the lists), and, although I'm not sure how long it will last, he is generally civil and forthcoming in them...
I don't know what to say about the packet filtering; is FreeBSD still filtering out packets from the OpenBSD networks, as they claim? "We won't stop filtering packets from the OpenBSD networks until Theo is out". Heh, it's fun to read archived threads sometimes.
Well, thanks for being honest; it's important for me to know how OpenBSD got its reputation. You seem like a good person, with very valid reasons for not using OpenBSD.
However, it's interesting to notice some people will pay good money for excellent software, even without being able to try it out first. If you're resourceful, you can even get OpenBSD for (close to) free, as you pointed out.
Some people find Theo's development style and anti-social behavior to be abrasive, but since when have those qualities stopped anyone from being a fantastic software developer? Consider Picasso for a moment; although you may find him intensely disagreeable as a person, does that mean you will never find meaning in his paintings?
I urge you to reconsider OpenBSD, if you are holding back simply because of Theo's personality. OpenBSD is a truly refined, unusual experience, and, trust me on this; you can enjoy the meal without liking the chef.
OpenBSD is fantastic for servers, especially if you don't need to run KDE or Gnome apps (although, I'm sure you could figure out how to run some o' them new-fangled window managers, if you are so inclined.) If you are looking for a desktop system, though, I'd look elsewhere. Personally I don't even install X11 if I can help it.
The encrypted swap feature is not one of the points that initially sold me on OpenBSD (although it does sound über-sexy at cocktail parties). =P
It's the other, shall I say, more practical (OK, all right, probably more boring, too; but...) features that I like. Like SSH built-in, and everything locked down by default. Not necessarily cutting-edge, but nice. I sleep well at night.
Well said. You seem to understand exactly how much benefit will come from having an awesome and intuitive GUI, evolved from a combination of the world's most popular GUI's and an awesome core OS.
You know, I agree with that. You really don't need to be running things as powerful as Bind.
Unfortunately, the default installations of many Linux distros seem to be getting more and more top-heavy. Even things like Bind and Sendmail are getting installed by default; I'm not sure if this is a good thing.
One thing I like about OpenBSD is the very sparse, almost Bauhaus-style install. You have to go through manually and set things up if you want to use them.
It seems like a lot of work, and it perhaps is very cumbersome if you've never done it before, but I just feel much more comfortable running an OS that doesn't have a whole bunch of crufty packages installed that I may or may not ever want or need.
The security audit for OpenBSD helps, too, though. ;-)
Thanks for the link, I'll check it out.
Shadowrun would be the ideal starting point for a MMRP. If people could get behind the Worldforge project, and use the Shadowrun series of books for the code base (being careful to not make the universes too close together, for obvious copyright reasons), it just might be the sort of project that would snowball into something wicked.
The real question is, will the Open Source model work for a large gaming project? Or is the budget constraint just too huge in comparison to the $oftware companie$?
Anyway, I'd love to see the Shadowrun universe online, in an immersive RPG.
Stupid article though.
However, a lot of companies are using Java for middleware and server-based applets (servlets).
I agree that the BSD's should think carefully before jumping in to every technology that happens along, but Java is already become entrenched in the enterprise. If a Java port comes out, that doesn't mean you suddenly *have* to install it on your BSD boxen.
I guess I just find it disturbing that the original poster was able to get away with posting such FUD, like "I trained in Java in the war of 1967", and "recent studies indicate that Java != bad coffee". If you don't like Java or BSD, fine. But don't post a bunch of crap just trying make a given technology look bad.
I was under the impression that Java, though initially it failed to live up to the cross-platform promises, was now running fairly well, with (mostly) portable code and a faster compile time, more standardization, etc.
Is it really that bad? Or are you just trying to get over a bad initial experience with Java?
As for seperate code bases maintained by seperate teams, that may indeed be one good way to develop, but I'm not sure if every project requires that much redundancy of effort.
Quality of service contracts are going to be the make-or-break deciding factor for ASP's. OpenBSD can provide the uptime an applications provider will need to meet that contract; it's been through a year and a half security audit (which happened to close many software bugs as a side benefit), and uptimes in the hundreds of days are common.
OpenBSD 2.7 comes out next week, with integrated SSH2 and a large collection of packages and ports!
Seriously, never heard of the Iron Chef before...anybody got any *working* links to any fan sites? I'd like to see what its all about.
I don't have cable....hmmm....maybe that's why. Guess I should refrain on commenting about the "Rights" aspect, since I have no idea what the show is about. ;-)
Most people don't need the reliability/security/speed of a BSD these days. Those that do, well, we seek them out. That's why market share for the BSDs is slipping; not because there aren't more BSD machines coming online, but because there are far more user machines (i.e. not bulletproof OpenBSD servers) proportionally coming online.
Believe me, when some of the larger sites out there start to find out that NT sucks harder than a Studebaker vacuum cleaner, and that Linux isn't the answer to everything (yeah yeah mod me down), there will be *many* conversions to BSD. Until then, market share will suffer as Linux continues to get the hype, NT continues to get the $ale$, and BSD continues to get overlooked.
The BSD's are a niche operating system. They are never going to have the mass appeal of a Windows GUI or a Windows GUI ripoff (KDE?), but that's OK; they don't need to. The BSDs attract people who are serious about building clean, stable, robust systems. They don't need to attract a large market share; the people who run BSD systems already aren't going to abandon them for Red Hat or NT anytime soon. Remember when Hotmail tried to move to NT?
It only took me about 6 months to figure out that I wanted to run OpenBSD on most of my servers. It might take other people longer, but they'll figure it out.
Oh, and I'd forget about a BSD "Summit" anytime soon; the grudges that caused the NetBSD/OpenBSD rift still sting a little too much.
Was there any part in particular you didn't like?