Yes, but the rest of us have written about 1000 times more code than you because we didn't spend our time checking a ton of assembly because we presume the compiler is flawed.
There are times when this sort of checking is acceptable if not required. The kernel is a good place to do it.
You aren't going to do this for KDE or Gnome however.
A bug exists with or without the optimization if the code you pasted is the actual code. tun being null makes the tun->sk reference invalid. You should end up with a panic at this point.
If the compiler optimized away the tun check without there being a previous tun check, there is also a compiler bug. The compiler shouldn't have assumed that tun was initialized just because it was read from, which is all a dereference is, a read and an add.
Really? Tell that to all the apps that are PAE aware, MSSQL server for instance.
Its the same as using the old segmented memory model from a practical perspective, although the OSes today use a completely different API for accessing the other memory.
Windows is certainly overpriced, no argument there.
I would argue however that the OS is probably the single largest and most important component of the PC. While its not a piece of hardware, and it is just one of many required components, its the one that matters the most, I think.
I mean, change your ram manufacture, you probably won't notice. Mobo, processor, case, power supply, all these things can change a fair amount and in most cases won't provide an immediately noticeable difference. The software running on them for the most part won't care.
Change the OS and the world just changed. All of your other software needs to be changed in most cases, save for FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.
Either way, unless your software requires Windows, I can't imagine why you wouldn't use a free OS for your rendering farm. Its something you shouldn't really directly interact with after it is setup. Even if you prefer Windows the desktop/workstation (I do personally) I can't imagine why would would waste the money on licenses when you're probably going to get far superior performance out of something like a cut down, bare bones Linux or FreeBSD install.
Truth be told, the guy writing the article really isn't all that knowledgeable, as you can tell by his take on how much memory you should use and its limitations mentioned in my other post.
For memory, 4 GB is a good start. With the availability of inexpensive 4 GB kits (reviewed here), there's no reason not to. If you are using a dual-core processor and your renderer is a 32-bit application, then 4 GB means you'd have just short of the maximum RAM for each core (which is a good idea if your renderer doesn't multi-thread properly).
This is where I got off. I wasn't aware that dual core processors treated ram separately. Thats news to me, and the guys at AMD, Intel, MS, and Linus as well. Every OS I'm aware of bases the memory available on the app, not the core, with most 32 bit OSes allowing for about 3G of memory usable to the app (roughly a gig is part of the kernel space for various things in most cases), and allowing for more with some kernel tuning depending on the OS. I think Linux allows for that, I know Windows and FreeBSD do.
I also guess he's never heard of PAE? Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing, meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so, and even without support directly in the application, you can run multiple processes to get the 3G or so per process, which with 2 processes you are at 6. So if your shitting rendering app is 32 bit, not PAE aware, single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage. With a real rendering app, i.e. multithreaded, PAE aware and still 32 bit, its a no brainer. Of course if you're going through the effort to do all this, what are the chances your renderer is going to be 32 bit instead of 64? This is a question I really do not know as I'm not a render monkey, but I just can't see anything that matters still being a 32 bit app unless RAM really doesn't matter in rendering, which lets face it, for a complex scene, it does.
Its good to know Tom's has some real techs working for him that understand how computers work.
Bypass machines are designed to circulate blood without the body doing it on its own, you just have to get it started before the blood coagulates and becomes too difficult to move.
2) Everyone tests. There is no test team. All developers test things before a release. He does not talk about agile and how everyone should be testing their own stuff anyways.
They do test their own stuff. They also test how their own stuff works with everyone elses changes rather than in a little sandbox on the side without interaction with all the other parts. This interaction is where you run into problems. Most developers can write small chunks of code that work fine when used exactly as expected, which is what the original developer will do since they know exactly how it was intended to be used. You get in trouble when I start using your code that you documented one way and I interpreted a different way, which you didn't bother to sanitize the input or properly error check, and I just assumed your code was going to work flawlessly. Now, through no fault of yours or mine directly, we've introduced a problem that neither one of us will notice when playing in our own little sandbox.
You point this out like its a bad thing, in reality this is the only way it should be done.
The developers who finish their work early are not sitting idle, they are testing. The sooner the testing gets done and everything is signed off on, the sooner everyone can move forward. It prevents you from just working on what you want to work on and leaving everyone else to do the dirty/unfun work.
Both of your points that you think are bad are just signs of selfishness on your part and a lack of willingness to be a team player. The world doesn't revolve around you or your code, sorry.
Get over it people. Theo's good at what he does, OpenBSD could and would not exist without him, and the world is a better place for it.
I have a great deal of respect for Theo and his work on OBSD, however we need to be realistic.
He's not THAT good. One of my biggest complaints is the whole 'no exploits in XXX time!@%$!@%' bullshit. Which just changes each time an exploit is found.
My code has never been exploited by anyone ever, including myself.
(two weeks later, after you exploit my code)
My code has never been exploited by anyone who hasn't ran it.
This is the kind of shit that gets pulled with OBSD, and makes it FAR FAR less impressive than it sounds if you actually have followed his antics over the past 10 years. Everytime someone shows him to be wrong, he just changes the definition. Anyone can be great if you just change the definition to fit your purposes. Why people still treat him like a god is beyond me.
He's a good developer, but his ability to be an obtuse asshole far overshadows his ability as a developer. I've found its far easier to just use one of the other BSDs which are far less painful and while not 'as secure' by Theo's definition, they good enough for production work and feel far less like you're living in the 70s when you use them.
Let Theo go play in his little sandbox, I don't mind, because he stands by the BSD license it means that my prefered OSes get to be pretty much as safe has OBSD, without me having to deal with all the headaches of his holier than thou attitude.
With that said, I respect and appreciate his (and ever other OBSD developers) work. It is definitely good stuff. Their skills are far above my level, no doubt. He is still just a man and should be treated as such, sans pedestal or high horse.
Use interwiki links. I use them to link our intranet, mediawiki, our external developer wiki, and our external support wiki.
You will probably be unable to use them since using them requires the ability to get off your lazy ass and read the MediaWiki documentation or google for it, which results in plenty of information.
Also the fact that you're going to have to be able to insert a row in a database is probably going to be over your head.
Yes, I know it works just fine, however they're claiming a vendor and product ID that is not their own in order to get it to work with iTunes, thats against the rules for devices that are supposed to USB compatible. Do they use the official USB compatible logo anywhere for the Pre? I'd think the USB folks themselves would be pissed off about that much like Phillips and those bullshit CD discs that were 'copy protected' from a few years back.
No, safari says its a mozilla compatible browser called Safari. And IE does roughly the same thing.
They don't say 'Hey, I am mozilla the browser' the say 'hey, I'm a mozilla compatible browser called: Safari version 4.0.112512, using WebKit 1.0.x' or whatever version it happens to be at the time.
The pre on the other hand says 'Hey, I'm an iPod!'
All of Europe will fit into a handful of America's states. Most of Europes countries will fit into some of the smaller US states. I'm too lazy to look it up again, but I seem to remember that the 3 largest US states ( Alaska, California, Texas) are roughly the size of a 1/3rd of Europe. Thats 3 of 50. Austria is roughly the size of Maine, which is one of our midsized states.
Europeans don't seem to realize that they are becoming just like America over time. The EU is basically with America was 200 years ago. Okay, so not exactly, but its not that different when you look at it as just a collection of states/countries in a larger union. Give it a couple centuries and Europe will be pretty much the same for all intents and purposes.
For reference, the largest country in Europe, the Ukraine is roughly 603,700km/2. Texas alone is 696,241km/2, and its only the second largest, which is a little more than half the size of the largest, Alaska. Thats assuming we don't count Canada, which lets face it, is just a state we don't want to call our own for various reasons. Which is okay, cause no Canadian would like that either:)
What really bothers me, as an American is when Americans fall into the whole 'Europe has so many different countries and cultures I want to visit'. This is true, no argument. However, if you really TRAVEL around America, other than sharing a common language, it has just as much if not more variance than Europe. People over look all of the culture they have in their own country just because we call our states 'state' rather than 'country'. Once the EU stops calling them countries and states referencing them as just states in the union, it really won't be anything different.
Again, this is neither good nor bad, whats bad is the fact that so few people recognize this, American, European or otherwise.
It makes Apple look so very close to Microsoft in attitude that I'm apalled. Embrace-and-extend doesn't mean spank your customers.
When you put it this way, then occasionally, I'm into a little embracing and extending, but only in the bedroom or well, anywhere else as long as she's hot, and only when I'm doing the embracing and extending.
When someone points out how you are a fanboy and wrong, that doesn't make them a Microsoft shill or incorrect. Most of the pro-microsoft stuff seen on slashdot is true, sure there is some BS, but there not really anymore MS BS than there is GPL/Linux BS spread here.
Turn off your damn fanboy paranoia for a few moments and realize that while they are fully evil bastards, they are simply better at some things than your precious. GPL and Linux aren't the end all be all/only solution that can possibly be for everything on the planet, regardless of how much you want it to be so. Its not going to make you cool even if it were true, you'll still be a dull douche bag following the trend set by someone else:)
Ahh... male enhancement that makes you 'thicker' and 'wider'... Off topic I know, but could someone explain to me how thicker and wider are different when referring to the penis?
Slashdot Mirror
Yes, but the rest of us have written about 1000 times more code than you because we didn't spend our time checking a ton of assembly because we presume the compiler is flawed.
There are times when this sort of checking is acceptable if not required. The kernel is a good place to do it.
You aren't going to do this for KDE or Gnome however.
A bug exists with or without the optimization if the code you pasted is the actual code. tun being null makes the tun->sk reference invalid. You should end up with a panic at this point.
If the compiler optimized away the tun check without there being a previous tun check, there is also a compiler bug. The compiler shouldn't have assumed that tun was initialized just because it was read from, which is all a dereference is, a read and an add.
Really? Tell that to all the apps that are PAE aware, MSSQL server for instance.
Its the same as using the old segmented memory model from a practical perspective, although the OSes today use a completely different API for accessing the other memory.
http://en.wikipedia.org/wiki/Physical_Address_Extension
I tried running SLS Linux on a 286 in somewhere between 92-96, doesn't work so well :(
Yes, I was young and ignorant then about why you REALLY DID have to have a 386 or better. I just figured it would be slower :/
Windows is certainly overpriced, no argument there.
I would argue however that the OS is probably the single largest and most important component of the PC. While its not a piece of hardware, and it is just one of many required components, its the one that matters the most, I think.
I mean, change your ram manufacture, you probably won't notice. Mobo, processor, case, power supply, all these things can change a fair amount and in most cases won't provide an immediately noticeable difference. The software running on them for the most part won't care.
Change the OS and the world just changed. All of your other software needs to be changed in most cases, save for FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.
Either way, unless your software requires Windows, I can't imagine why you wouldn't use a free OS for your rendering farm. Its something you shouldn't really directly interact with after it is setup. Even if you prefer Windows the desktop/workstation (I do personally) I can't imagine why would would waste the money on licenses when you're probably going to get far superior performance out of something like a cut down, bare bones Linux or FreeBSD install.
Truth be told, the guy writing the article really isn't all that knowledgeable, as you can tell by his take on how much memory you should use and its limitations mentioned in my other post.
http://hardware.slashdot.org/comments.pl?sid=1306469&cid=28734027
This is where I got off. I wasn't aware that dual core processors treated ram separately. Thats news to me, and the guys at AMD, Intel, MS, and Linus as well. Every OS I'm aware of bases the memory available on the app, not the core, with most 32 bit OSes allowing for about 3G of memory usable to the app (roughly a gig is part of the kernel space for various things in most cases), and allowing for more with some kernel tuning depending on the OS. I think Linux allows for that, I know Windows and FreeBSD do.
I also guess he's never heard of PAE? Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing, meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so, and even without support directly in the application, you can run multiple processes to get the 3G or so per process, which with 2 processes you are at 6. So if your shitting rendering app is 32 bit, not PAE aware, single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage. With a real rendering app, i.e. multithreaded, PAE aware and still 32 bit, its a no brainer. Of course if you're going through the effort to do all this, what are the chances your renderer is going to be 32 bit instead of 64? This is a question I really do not know as I'm not a render monkey, but I just can't see anything that matters still being a 32 bit app unless RAM really doesn't matter in rendering, which lets face it, for a complex scene, it does.
Its good to know Tom's has some real techs working for him that understand how computers work.
Bypass machines are designed to circulate blood without the body doing it on its own, you just have to get it started before the blood coagulates and becomes too difficult to move.
Wait wait wait!! You mean someone actually uses OpenBSD for something OTHER than a firewall? That sounds silly to me.
Either way, FBSD is a far superior firewall, and when you install it in the same manner that OBSD installs its just as secure.
OBSD is 'secure' because they don't install or start any services they don't have to. Once you add an open port its claim to fame is gone.
FBSD when installed in the same way has the same track record, and a far better networking stack.
The main difference is, OBSD is just a pain in the ass to use regardless of how you install it.
FBSD isn't nearly as much of a pain in the ass, regardless of how you install it.
I really have never understood why people get so excited over OBSD, its not really that impressive.
If you count Linux as a Unix, you must count OS X, since OS X is actually a certified unix and Linux isn't.
Uhm, you do realize, thanks to things like OS X, that it IS the most predominate Unix in the world right? x86 or otherwise.
Please feel free to show me a unix (and we'll use the term loosely as to not rule out Linux) with more installed machines.
They do test their own stuff. They also test how their own stuff works with everyone elses changes rather than in a little sandbox on the side without interaction with all the other parts. This interaction is where you run into problems. Most developers can write small chunks of code that work fine when used exactly as expected, which is what the original developer will do since they know exactly how it was intended to be used. You get in trouble when I start using your code that you documented one way and I interpreted a different way, which you didn't bother to sanitize the input or properly error check, and I just assumed your code was going to work flawlessly. Now, through no fault of yours or mine directly, we've introduced a problem that neither one of us will notice when playing in our own little sandbox.
You point this out like its a bad thing, in reality this is the only way it should be done.
The developers who finish their work early are not sitting idle, they are testing. The sooner the testing gets done and everything is signed off on, the sooner everyone can move forward. It prevents you from just working on what you want to work on and leaving everyone else to do the dirty/unfun work.
Both of your points that you think are bad are just signs of selfishness on your part and a lack of willingness to be a team player. The world doesn't revolve around you or your code, sorry.
I have a great deal of respect for Theo and his work on OBSD, however we need to be realistic.
He's not THAT good. One of my biggest complaints is the whole 'no exploits in XXX time!@%$!@%' bullshit. Which just changes each time an exploit is found.
My code has never been exploited by anyone ever, including myself.
(two weeks later, after you exploit my code)
My code has never been exploited by anyone who hasn't ran it.
This is the kind of shit that gets pulled with OBSD, and makes it FAR FAR less impressive than it sounds if you actually have followed his antics over the past 10 years. Everytime someone shows him to be wrong, he just changes the definition. Anyone can be great if you just change the definition to fit your purposes. Why people still treat him like a god is beyond me.
He's a good developer, but his ability to be an obtuse asshole far overshadows his ability as a developer. I've found its far easier to just use one of the other BSDs which are far less painful and while not 'as secure' by Theo's definition, they good enough for production work and feel far less like you're living in the 70s when you use them.
Let Theo go play in his little sandbox, I don't mind, because he stands by the BSD license it means that my prefered OSes get to be pretty much as safe has OBSD, without me having to deal with all the headaches of his holier than thou attitude.
With that said, I respect and appreciate his (and ever other OBSD developers) work. It is definitely good stuff. Their skills are far above my level, no doubt. He is still just a man and should be treated as such, sans pedestal or high horse.
Or perhaps hindsight is 20/20.
Use interwiki links. I use them to link our intranet, mediawiki, our external developer wiki, and our external support wiki.
You will probably be unable to use them since using them requires the ability to get off your lazy ass and read the MediaWiki documentation or google for it, which results in plenty of information.
Also the fact that you're going to have to be able to insert a row in a database is probably going to be over your head.
READ THE DOCUMENTATION YOU LAZY FUCK.
Funny, GPL is about preventing limits on what users can do with their software ... by adding limits on what users can do with their software.
I'm so sick of seeing you idiotic fanboys using this battle cry yet being too stupid to see the hypocrisy in the statement.
Technically.
Yes, I know it works just fine, however they're claiming a vendor and product ID that is not their own in order to get it to work with iTunes, thats against the rules for devices that are supposed to USB compatible. Do they use the official USB compatible logo anywhere for the Pre? I'd think the USB folks themselves would be pissed off about that much like Phillips and those bullshit CD discs that were 'copy protected' from a few years back.
No, safari says its a mozilla compatible browser called Safari. And IE does roughly the same thing.
They don't say 'Hey, I am mozilla the browser' the say 'hey, I'm a mozilla compatible browser called: Safari version 4.0.112512, using WebKit 1.0.x' or whatever version it happens to be at the time.
The pre on the other hand says 'Hey, I'm an iPod!'
Well you don't have to use the latest version of iTunes, theres no law that requires it.
You can do whatever you want with your iPhone or iPod, just don't expect Apple to support it.
No different than ... (car analogy rolling in) cars.
Go ahead and put a corvette engine in your mazda miata. Its been done. Don't expect GM OR Mazda to service or warranty it anymore however.
Note: Apple isn't even in the mp3 business, it doesn't even sell mp3s. It makes players that will play them, but it doesn't sell them.
I realize you're really referencing 'audio files of a reasonable size for use on average devices' or something like that, but I'm just being pedantic.
All of Europe will fit into a handful of America's states. Most of Europes countries will fit into some of the smaller US states. I'm too lazy to look it up again, but I seem to remember that the 3 largest US states ( Alaska, California, Texas) are roughly the size of a 1/3rd of Europe. Thats 3 of 50. Austria is roughly the size of Maine, which is one of our midsized states.
Europeans don't seem to realize that they are becoming just like America over time. The EU is basically with America was 200 years ago. Okay, so not exactly, but its not that different when you look at it as just a collection of states/countries in a larger union. Give it a couple centuries and Europe will be pretty much the same for all intents and purposes.
For reference, the largest country in Europe, the Ukraine is roughly 603,700km/2. Texas alone is 696,241km/2, and its only the second largest, which is a little more than half the size of the largest, Alaska. Thats assuming we don't count Canada, which lets face it, is just a state we don't want to call our own for various reasons. Which is okay, cause no Canadian would like that either :)
What really bothers me, as an American is when Americans fall into the whole 'Europe has so many different countries and cultures I want to visit'. This is true, no argument. However, if you really TRAVEL around America, other than sharing a common language, it has just as much if not more variance than Europe. People over look all of the culture they have in their own country just because we call our states 'state' rather than 'country'. Once the EU stops calling them countries and states referencing them as just states in the union, it really won't be anything different.
Again, this is neither good nor bad, whats bad is the fact that so few people recognize this, American, European or otherwise.
I do think this is bullshit on apples part.
However ... if you think the Pre is a 'drop in replacement' for an iPhone than you've not used one of the two devices, possibly neither.
Nope, this guy is just a bad troll, take a look at the rest of his posts and you'll see what I mean.
When you put it this way, then occasionally, I'm into a little embracing and extending, but only in the bedroom or well, anywhere else as long as she's hot, and only when I'm doing the embracing and extending.
When someone points out how you are a fanboy and wrong, that doesn't make them a Microsoft shill or incorrect. Most of the pro-microsoft stuff seen on slashdot is true, sure there is some BS, but there not really anymore MS BS than there is GPL/Linux BS spread here.
Turn off your damn fanboy paranoia for a few moments and realize that while they are fully evil bastards, they are simply better at some things than your precious. GPL and Linux aren't the end all be all/only solution that can possibly be for everything on the planet, regardless of how much you want it to be so. Its not going to make you cool even if it were true, you'll still be a dull douche bag following the trend set by someone else :)
Ahh ... male enhancement that makes you 'thicker' and 'wider' ... Off topic I know, but could someone explain to me how thicker and wider are different when referring to the penis?