Mac OS X has been based on BSD for the following reason: OS X is actually a very new version of NeXTSTEP/OPENSTEP/etc. The original *STEP versions ran on a Mach microkernel with a 4.4BSD personality. So Jobs chose BSD because the old NEXT stuff ran on BSD, so to speak. This has, well, absolutely nothing to do with the SCO suit.
No please don't. I actually need if_rl.c, since I own and use those wretched RealTek NICs. Actually, removing it will actually cause a lot more problems that it would solve...
Oh, and if_rl.c is great reading material. I love how the comments in that file blast RealTek to hell and back.:)
No, it's part of the RELENG_5_1 branch. CURRENT is the head branch. Sure, it's not stable, but it's a RELEASE and does get maintained seperately, just like the RELENG_4_[something] branches are being maintained.
Note that no new features are added to the RELENG_[Major]_[Minor] branches, just bugfixes and security updates.
Dijkstra had a very distinctive and very readable handwriting. It certainly influenced mine. I don't know which pens he used, but I do agree there is something about writing stuff by hand. For one, you write slower than you think. And it can be a really meditative experience putting words to paper by hand.
Oh, I found a little page on the sara website where it is clarified (can't get onto the intranet anymore, else I'd have mirrored some better specs). Anyway, more about TERAS here.
Nope, the Origin 3800 at this place has 1024 procs. That's where I worked. You're behind the times, so to speak. Europe has big fast number crunching behemoths too.
I was of course overreacting. The machine is expensive. The machine has 1024 procs, big fat arrays of scsi disks (think multiple multiple terabyte storage, raid5 and mirrored (can't say how much, it's too long ago, but it was heaps. Several room filling cabinets full of just SCSI disks), and really shitloads of RAM (think terabytes in total). It's probably not a billion dollars, but it's certainly quarter way if you count support contracts and upkeep.
I was actually surprised that the thing managed to run for about an half an hour on just the nobreak, together with a Cray and a 256 node Beowulf cluster which we did manage to gracefully shut down in time. If we had the power generators ready (they were due to be operational in the next few days), they could've ran for almost forever without a power faillure.
Ain't Finnagle a bitch.
Of course I don't work there anymore. And no, I wasn't fired over this. Nobody was. The contracter that didn't make with the backup power (and the power company for causing a 5 hour power blackout) did get a hefty bill though.
I've experienced it the other wat around once. At some previous $workplace, we had this humongous SGI Origin 3800 cluster. Due to a city-wide brown out, and due to the fact that we were just installing the diesel-powered generators, the thing had to survive for a couple of hours on the nobreak. Sure, all the lights in the building were out, but the behemoth was still churning. We (the venerable sysadmins) were trying to decouple a partition so we could hook up a console to ot to bring down the thing gracefully. Of course, that wasn't that easy.
Suddenly the nobreak was all out, and the billion dollar machine went *poof* - down. Damage? A couple of SCSI disks, but of course everything was mirrored and had parity so even with the damaged disks, there was no data loss.
Then (after a few hours) the powerfaillure ended, the lights went back on in the building, but the lights on the big cluster were still off. The other way round than you'd like to see. Although, when the building power was out, and the nobreak for the machine was active, it sure was a pretty sight. Although, with the impending doom, I didn't really have time to appreciate it.
That's an interesting piece of fiction. Guess I'm lucky I'm not a UNIX coder but more of a FreeBSD coder.:-)
There's also a lot of stereotypical imagery in your story. Did you know that, yes, lots of people in the Open Source world are gay (Eric Allman is, Alan Turing is, to name but a few). Needless to say, without mr. Turing's efforts, you wouldn't be typing this story on this website. A little more respect for people's sexual preference please. I'm not homosexual, but many of my friends are. And sure, there might be some asshats around, but I can assure you they are in the minority.
Are you sure this isn't just misdirected homophobia? Oh well, we will never find out, since you are an anonymous coward.
(and no, Free/Net/OpenBSD and Linux are not UNIXen, and you desperately need a girl/boyfriend. Or a life. Maybe both)
Don't forget bzflag.... Ooohhhhhh bzflag... many hours until the wee hours in the morning I played that wretched game. Or nethack, or rogue... or hunt the $%(^%(^$@ wumpus.
Don't say the *nixen don't have addictive games...
Why do us BSD people like BSD so much? Because it gets us laid. Never mind those whiney Linux geekoids. BSD lets you grow a beard and long hair, and you'll still be attractive to the opposite sex.
One caveat though, you do need to shower or bathe every once in a while. Although girls can't resist the looks of a bearded and long-haired daemon totin' ruffian, if you don't take care of your personal hygiene, the girls will approach, and then flee again.
So there you have it. Us BSD folk are in it for the chicks. BSD is not dying, it's a geek's ticket to having a shot at procreating himself!
(for the humor impaired, I'm not being serious. Yes I am a bearded, long haired geek and no, I don't have troubles meeting/talking to the opposite sex, but I doubt that BSD as anything to do with that...)
[loki:~] coolvibe% setenv EDITOR %p [loki:~] coolvibe% chsh chsh: 0x1: No such file or directory chsh:/etc/master.passwd: unchanged [loki:~] coolvibe% uname -a Darwin loki.ipv6.hackerheaven.org 6.6 Darwin Kernel Version 6.6: Thu May 1 21:48:54 PDT 2003; root:xnu/xnu-344.34.obj~1/RELEASE_PPC Power Macintosh powerpc
I have seven machines here. One is the router/rtadvd box. All have entries in the nameserver.
Anyway, there's more than one way to supply ipv6 ip adresses to a machine. Another way is dhcp6, and manual assignment. All you need to know is what subnet your machines belong to. I have a/48, so I know what part is mine to control, and what part isn't.
I can choose for using a EUIN based adressing scheme based on MAC adresses in my network, or I can just refer to my machines as subnet:1 subnet:2 etc etc etc.
It's not much harder than the current scheme with ipv4, other than I have lots more room to play with
Since the Winsock emulates the BSD calling interface (with some WSA_* handwaving in advance), the problem is apps using ipv4-only functions like gethostbyname, gethostbyaddr and using PF_INET. The solution is having the apps use getaddrinfo and PF_UNSPEC and let the resolver figure out itself what is best.
Using the addrinfo structures to hold resolver data breeds apps that can do both ipv4 _and_ ipv6. As far as I know, winsock groks the addrinfo stuff. People just need to use it.
Yup. These solve many problems I've had with the driver overwriting the %gs register in multithreaded OpenGL apps. It made apps SIGSEGV on exit. KDE (well, actually Qt) was very much affected, and one of the "fixes" was compiling Qt WITHOUT OpenGL support.
The SIGSEGV "crashes" are totally gone, and these drives drive my GeForce 4 MX much (yeah, I know, cheap card) faster too. Tuxracer really runs very smooth!:)
Anyway, these run mighty nice on my 5.1-RELEASE system. People that claim that BSD is dead plain don't know what they are blabbing about.
When you use X on your local host, it doesn't really use the network stack. Read up on pipes and domain sockets before you spout off like that. You can still use X without having network support in your kernel. You only need sockets Ergo, nothing moves across any network. So all your points are basically uninformed drivel.
Domain sockets (like the ones X uses locally) are a very efficient way to do IPC. Every write() on a domain socket in in practice a memcpy/memmove operation. So the overhead is really really small. And you get network transparancy basically for free. It has _no_ impact whatsoever on what you do locally.
If you want to point the blame at the "slowness" of X, blame the toolkits. GTK is slow. Motif is slow. Qt is slow. Xlib is VERY fast, but cumbersome to use.
Slashdot Mirror
Allright, so I suck at puns. Byte me.
Great, you just killed the german slashdot readership. Happy now?
(I'm single, although I am seeing people... Sex hasn't turned me off of my geekish prowess anyway)
Mac OS X has been based on BSD for the following reason: OS X is actually a very new version of NeXTSTEP/OPENSTEP/etc. The original *STEP versions ran on a Mach microkernel with a 4.4BSD personality. So Jobs chose BSD because the old NEXT stuff ran on BSD, so to speak. This has, well, absolutely nothing to do with the SCO suit.
I said 1024 proc "cluster", didn't I? And yes, a TB of ram is about right. The plural thing was just a brainfart.
Oh, and if_rl.c is great reading material. I love how the comments in that file blast RealTek to hell and back. :)
Note that no new features are added to the RELENG_[Major]_[Minor] branches, just bugfixes and security updates.
What does me living somewhere in a dodecahedral shape have to do with what timezone I live in?
Oh you mean geographic, not geometric... Never mind...
Dijkstra had a very distinctive and very readable handwriting. It certainly influenced mine. I don't know which pens he used, but I do agree there is something about writing stuff by hand. For one, you write slower than you think. And it can be a really meditative experience putting words to paper by hand.
Oh, I found a little page on the sara website where it is clarified (can't get onto the intranet anymore, else I'd have mirrored some better specs). Anyway, more about TERAS here.
Nope I'm not. You are right that it originally was 256, then 512, but now it's 1024.
Nope, the Origin 3800 at this place has 1024 procs. That's where I worked. You're behind the times, so to speak. Europe has big fast number crunching behemoths too.
I was actually surprised that the thing managed to run for about an half an hour on just the nobreak, together with a Cray and a 256 node Beowulf cluster which we did manage to gracefully shut down in time. If we had the power generators ready (they were due to be operational in the next few days), they could've ran for almost forever without a power faillure.
Ain't Finnagle a bitch.
Of course I don't work there anymore. And no, I wasn't fired over this. Nobody was. The contracter that didn't make with the backup power (and the power company for causing a 5 hour power blackout) did get a hefty bill though.
Suddenly the nobreak was all out, and the billion dollar machine went *poof* - down. Damage? A couple of SCSI disks, but of course everything was mirrored and had parity so even with the damaged disks, there was no data loss.
Then (after a few hours) the powerfaillure ended, the lights went back on in the building, but the lights on the big cluster were still off. The other way round than you'd like to see. Although, when the building power was out, and the nobreak for the machine was active, it sure was a pretty sight. Although, with the impending doom, I didn't really have time to appreciate it.
There's also a lot of stereotypical imagery in your story. Did you know that, yes, lots of people in the Open Source world are gay (Eric Allman is, Alan Turing is, to name but a few). Needless to say, without mr. Turing's efforts, you wouldn't be typing this story on this website. A little more respect for people's sexual preference please. I'm not homosexual, but many of my friends are. And sure, there might be some asshats around, but I can assure you they are in the minority.
Are you sure this isn't just misdirected homophobia? Oh well, we will never find out, since you are an anonymous coward.
(and no, Free/Net/OpenBSD and Linux are not UNIXen, and you desperately need a girl/boyfriend. Or a life. Maybe both)
+5 funny
Don't say the *nixen don't have addictive games...
Why do us BSD people like BSD so much? Because it gets us laid. Never mind those whiney Linux geekoids. BSD lets you grow a beard and long hair, and you'll still be attractive to the opposite sex.
One caveat though, you do need to shower or bathe every once in a while. Although girls can't resist the looks of a bearded and long-haired daemon totin' ruffian, if you don't take care of your personal hygiene, the girls will approach, and then flee again.
So there you have it. Us BSD folk are in it for the chicks. BSD is not dying, it's a geek's ticket to having a shot at procreating himself!
(for the humor impaired, I'm not being serious. Yes I am a bearded, long haired geek and no, I don't have troubles meeting/talking to the opposite sex, but I doubt that BSD as anything to do with that...)
Hmm? Smells like a formatting bug
Anyway, there's more than one way to supply ipv6 ip adresses to a machine. Another way is dhcp6, and manual assignment. All you need to know is what subnet your machines belong to. I have a /48, so I know what part is mine to control, and what part isn't.
I can choose for using a EUIN based adressing scheme based on MAC adresses in my network, or I can just refer to my machines as subnet:1 subnet:2 etc etc etc.
It's not much harder than the current scheme with ipv4, other than I have lots more room to play with
Since the Winsock emulates the BSD calling interface (with some WSA_* handwaving in advance), the problem is apps using ipv4-only functions like gethostbyname, gethostbyaddr and using PF_INET. The solution is having the apps use getaddrinfo and PF_UNSPEC and let the resolver figure out itself what is best.
Using the addrinfo structures to hold resolver data breeds apps that can do both ipv4 _and_ ipv6. As far as I know, winsock groks the addrinfo stuff. People just need to use it.
*turns on rtsold in rc.conf*
*watches machine do RA queries*
hey,whaddayaknow, it configures itself! damn, that was hard...
Mods? Mod this up. It's very informative.
The SIGSEGV "crashes" are totally gone, and these drives drive my GeForce 4 MX much (yeah, I know, cheap card) faster too. Tuxracer really runs very smooth! :)
Anyway, these run mighty nice on my 5.1-RELEASE system. People that claim that BSD is dead plain don't know what they are blabbing about.
When you use X on your local host, it doesn't really use the network stack. Read up on pipes and domain sockets before you spout off like that. You can still use X without having network support in your kernel. You only need sockets Ergo, nothing moves across any network. So all your points are basically uninformed drivel.
Domain sockets (like the ones X uses locally) are a very efficient way to do IPC. Every write() on a domain socket in in practice a memcpy/memmove operation. So the overhead is really really small. And you get network transparancy basically for free. It has _no_ impact whatsoever on what you do locally.
If you want to point the blame at the "slowness" of X, blame the toolkits. GTK is slow. Motif is slow. Qt is slow. Xlib is VERY fast, but cumbersome to use.