Note: I'm not saying that X-Box/DC compatiblity would be a bad thing. Only that Sega denied the rumors before, and it would be delightfully ironic if they embraced it now.
The changes between 4.1 and 4.2 were hardly affected by BSDi. It was the same 'ol, same 'ol- bugfixes, a couple new features, and general improvements.
You won't see much from the BSD/OS code that was released to FreeBSD developers until, maybe 5.0. SMPng is BSD/OS "inspired" but their design does vary significantly from BSD/OS's.
Actually, any ham radio operator or FCC employee would tell you that the entire spectrum in this country belongs to the people of the United States of America. Hughes, et. al only license the right to use these airwaves- Just because you've paid the toll, you don't own the road.
If the signal wasn't encrypted, I would argue that watching it should be legal. As it is encrypted, I can only possibly fathom that it should be legal if one were to develop all of the technology to receive and unencrypt the signal in a clean-room enviornment. Fat chance.
Ok, I am the AC that had the original post WRT this topic that's since been moderated up to 4: Informative (I post regurarly, it gets moderated down, I post AC, it goes up. Who woulda thunk it?) and perhaps I'm being misunderstood.
Yes, it's a good thing. Congratulations Linux folks, I'm sure you did a good job, having stateful firewalls are handy for everyone to have. I don't mean to say the typical "we've had this for X years"
My issue was, and still is, mainly with the slashdot title. Why it rocks. It doesn't generally rock, it just rocks compared to the implementation in Linux 2.2.
Now, if the article had been "Why it's a great improvement over 2.2" that would have been great, and I would have continued on my day. But the fact that the title makes it seem revolutionary, when it's actually quite evolutionary, made me step up to the plate.
What rocks? Stateful firewalling. Does the article discuss Linux's implementation in detail, explaining why it's better than other stateful filters? No. It discusses the old and proven technique of stateful firewalling, and therefore tries to further Linux based on that alone.
I don't think that the original poster cared about Aqua. I don't. If (and I am considering it) I get a G4 for running OS/X, my advantage would be being able to run Macintosh applications (including games like Starcraft) on a UNIX system with a nice graphics rendering engine (Quartz, baby, quartz!)
What my unix box needs now is a nicer rendering engine. We'll see where XFree86 takes us!
There's always the option of their usual response to GPF- a little bomb warning you of the error made.
So what they're called segfaults under UNIX? A GPF is a GPF, they exist on every protected mode processor. As for what happens if Quartz crashes, it'd probably just take you back with a warning, and give you the chance to restart Quartz (or perhaps do it automatically.)
I rent DVDs for $5, when with DIVX I could have "purchased" the physical item. Besides the convience of having it closer for more replays (paying the $5 again), or being able to buy it for life ($20), I have nothing when I return it to Blockbuster. And late fees? Pfft.
And what would have made DIVX even more tempting if it caught on was the opportunity to hack the player to play "expired" disks.
So what I'm saying here is.. I don't know what I'm saying. In DIVX it's a good idea, because a video disk is an item you'd perhaps rent. But for a computer? I like my comptuers big, grey, and power hungry. I'm barely sold on the concept of batteries, let alone in computers.
I can rebut that with not one statistic and only pure logic.
Entering "sleep mode" causes your drives to spin down. And when you come out of sleep, you still incurr the expense (which I believe to be relatively small, by the way) of having to spin the drives back up.
So, not just do you have the problem of having to spin them back up when you resume work on your computer, but you're also wasting all of the power by just keeping the computer running. Things still operate in idle cycles; if they didn't, your computer would be cool after leaving it idle.
As for more general wasting of electricity that's easily preventable, in a Nuts and Volts article from some time last year covers it well- interesting stuff, talking about power consumption of devices that are turned off.
Well for starters you lose all those lovely ease of use features once you start using X instead of aqua. So there goes that.
Who said anything about using X instead of aqua?
I would guess that ports of GTK+, Qt, and perhaps other toolkits (Motif maybe?) are not far behind. Then, you have them all running on aqua. And that's sweet.
You should also note that TrustedBSD is a patchkit to FreeBSD that will most likely be fully merged with FreeBSD in the near future. It's not an OS, and it doesn't do any "auditings" that would concern it with the ports system. It's working to provide better security through smarter security, not just safer (but powerful) binaries like OpenBSD.
They're using FreeBSD on Mach, which provides quite a bit of low level harwdware specific services. I'd imagine that all they had to do is write or port drivers for the hardware that they're running on..
Not 3.2BSD on top of Mach, FreeBSD 3.2 on top of Mach. There was never a version 3.2 of Berkeley UNIX- AFAIK it went straight from 3BSD to 4BSD.
If you actually look at Darwin source, you'll see that there's also a lot of the userland taken from NetBSD.
Anyhow, Apple has definetly been a good neighbor to the open source world. Look at Darwin- people can take work from there back to FreeBSD or any other OS. They've also taken an interest in OpenPackages and it'll be interesting to see where, if anywhere, they go with that.
you dont have the pthread library installed. Go get it, install it and try again. This is nothing like the trouble you have getting stuff to compile on *BSD.
That's right, because on any recent BSD, you have a ports collection. cd/usr/ports/misc/foobar && make install, you're done. Nothing like the trouble on Slackware!
And don't argue that it's harder to compile non-ported software. I have written and maintain a couple FreeBSD ports, and I'll tell you that it's nothing more than a few minutes of effort. Most people are good at writing portable code, you know.
Re:Another alternative to Gore-Tex?
on
Nano-pants
·
· Score: 2
Did you read the article? It was designed to pass sweat.
Heck, it says that even in the summary up top; now, do you disagree? If so, why?
It's a widely held belief that gaming companies sell the console at a loss, and then recoup their expenses from the licensing fees that they can charge with an established customer base.
If SoA is supporting this, does this mean that they just don't realize that people who buy a Dreamcast solely to run NetBSD are costing them money? Or do they take the safer (much safer) guess that someone who bought it for NetBSD would also pick up a couple games? Or are they not selling them at a loss?
The advertising clause is totally different from the copyright reproduction clause. One requires that all advertising materials must give credit, and the other says that in source redistribution, the copyright/license MUST remain intact, and in binary redistribution, it must be included with the supplied materials.
The advertising clause was the only thing that was removed. Go read a copy of the license for more understanding, if you'd like.
It's been done, and applied to NFS and others, for quite a while. The freebsd-announce mailing list would be a good place to check for more; substantial work on it has been done for several months.
As for Linux, it's soomething that just came into 2.4 with one of the TUX patches in Q3 2000, as far as I know (source: http://boudicca.tux.org/hypermail/linux-kernel/200 0week36/0979.html)
"He's as blind as he can be, just see what he wants to see, nowhere man can you see me at all?"
Slashdot Mirror
Perhaps your problem is with the proprietary nature of the PS/2. PS/2 keyboards, anyone?
What makes a PC "IBM Compatible" is the system as a whole, mainly, the BIOS and the processor.
Change the BIOS considerably, and you aren't IBM compatible.
Because a buffer overflow in TUX would lead to total system comprimise.
Note: I'm not saying that X-Box/DC compatiblity would be a bad thing. Only that Sega denied the rumors before, and it would be delightfully ironic if they embraced it now.
The changes between 4.1 and 4.2 were hardly affected by BSDi. It was the same 'ol, same 'ol- bugfixes, a couple new features, and general improvements.
You won't see much from the BSD/OS code that was released to FreeBSD developers until, maybe 5.0. SMPng is BSD/OS "inspired" but their design does vary significantly from BSD/OS's.
If the signal wasn't encrypted, I would argue that watching it should be legal. As it is encrypted, I can only possibly fathom that it should be legal if one were to develop all of the technology to receive and unencrypt the signal in a clean-room enviornment. Fat chance.
And all versions require copyright reproduction. But with online help documents and thick manuals, that's really not too hard.
Yes, it's a good thing. Congratulations Linux folks, I'm sure you did a good job, having stateful firewalls are handy for everyone to have. I don't mean to say the typical "we've had this for X years"
My issue was, and still is, mainly with the slashdot title. Why it rocks. It doesn't generally rock, it just rocks compared to the implementation in Linux 2.2.
Now, if the article had been "Why it's a great improvement over 2.2" that would have been great, and I would have continued on my day. But the fact that the title makes it seem revolutionary, when it's actually quite evolutionary, made me step up to the plate.
What rocks? Stateful firewalling. Does the article discuss Linux's implementation in detail, explaining why it's better than other stateful filters? No. It discusses the old and proven technique of stateful firewalling, and therefore tries to further Linux based on that alone.
What my unix box needs now is a nicer rendering engine. We'll see where XFree86 takes us!
So what they're called segfaults under UNIX? A GPF is a GPF, they exist on every protected mode processor. As for what happens if Quartz crashes, it'd probably just take you back with a warning, and give you the chance to restart Quartz (or perhaps do it automatically.)
I rent DVDs for $5, when with DIVX I could have "purchased" the physical item. Besides the convience of having it closer for more replays (paying the $5 again), or being able to buy it for life ($20), I have nothing when I return it to Blockbuster. And late fees? Pfft.
And what would have made DIVX even more tempting if it caught on was the opportunity to hack the player to play "expired" disks.
So what I'm saying here is.. I don't know what I'm saying. In DIVX it's a good idea, because a video disk is an item you'd perhaps rent. But for a computer? I like my comptuers big, grey, and power hungry. I'm barely sold on the concept of batteries, let alone in computers.
Entering "sleep mode" causes your drives to spin down. And when you come out of sleep, you still incurr the expense (which I believe to be relatively small, by the way) of having to spin the drives back up.
So, not just do you have the problem of having to spin them back up when you resume work on your computer, but you're also wasting all of the power by just keeping the computer running. Things still operate in idle cycles; if they didn't, your computer would be cool after leaving it idle.
As for more general wasting of electricity that's easily preventable, in a Nuts and Volts article from some time last year covers it well- interesting stuff, talking about power consumption of devices that are turned off.
With the pixel-by-pixel antics of xlib, even by fully porting the API to aqua, you'll be wasting most of the potential of display PDF.
BSD/OS is the traditional name for BSDI(now BSDi)'s software. They call it the Internet Super Server now or something.
SunOS (and consquently Solaris; they didn't throw away the sourcebase to go to SVR4, you know), NeXT, BSD/OS.
Who said anything about using X instead of aqua?
I would guess that ports of GTK+, Qt, and perhaps other toolkits (Motif maybe?) are not far behind. Then, you have them all running on aqua. And that's sweet.
You should also note that TrustedBSD is a patchkit to FreeBSD that will most likely be fully merged with FreeBSD in the near future. It's not an OS, and it doesn't do any "auditings" that would concern it with the ports system. It's working to provide better security through smarter security, not just safer (but powerful) binaries like OpenBSD.
They're using FreeBSD on Mach, which provides quite a bit of low level harwdware specific services. I'd imagine that all they had to do is write or port drivers for the hardware that they're running on..
If you actually look at Darwin source, you'll see that there's also a lot of the userland taken from NetBSD.
Anyhow, Apple has definetly been a good neighbor to the open source world. Look at Darwin- people can take work from there back to FreeBSD or any other OS. They've also taken an interest in OpenPackages and it'll be interesting to see where, if anywhere, they go with that.
That's right, because on any recent BSD, you have a ports collection. cd /usr/ports/misc/foobar && make install, you're done. Nothing like the trouble on Slackware!
And don't argue that it's harder to compile non-ported software. I have written and maintain a couple FreeBSD ports, and I'll tell you that it's nothing more than a few minutes of effort. Most people are good at writing portable code, you know.
Heck, it says that even in the summary up top; now, do you disagree? If so, why?
If SoA is supporting this, does this mean that they just don't realize that people who buy a Dreamcast solely to run NetBSD are costing them money? Or do they take the safer (much safer) guess that someone who bought it for NetBSD would also pick up a couple games? Or are they not selling them at a loss?
The advertising clause was the only thing that was removed. Go read a copy of the license for more understanding, if you'd like.
It's been done, and applied to NFS and others, for quite a while. The freebsd-announce mailing list would be a good place to check for more; substantial work on it has been done for several months.
As for Linux, it's soomething that just came into 2.4 with one of the TUX patches in Q3 2000, as far as I know (source: http://boudicca.tux.org/hypermail/linux-kernel/200 0week36/0979.html)
"He's as blind as he can be, just see what he wants to see, nowhere man can you see me at all?"
A poster explained it well here: http://daily.daemonnews.org/view_story.php3?story_ id=1485