The dealer is not going to be equipped in most cases to deal with what looks like a software problem unless the software problem has already been resolved with a firmware update.
They can't rewrite the software, they can only load new firmware provided by the engineers.
I just made the switch to FiOS... I'm pretty happy with it.
So far, it's been like dealing with a totally different company when dealing with anything related to FiOS. They show none of their old nickel-and-diming that they did on the normal phone service, and they have been very responsive.
Not only that, when they got to my house, we didn't have a fiber drop to the house (it was at the end of the block), so the tech called his boss, who sent a truck full of people to dig the trench and run the line the rest of the way to the house (across several neighbors' yards). When they were done they cleaned it all up so well you wouldn't even know they had been there.
The combined install time for Cable and Fiber was about 6 hours I think, but I wasn't there for the whole thing.
I've been running -CURRENT since before the libpthread integration, and I still have apps that I've been too lazy to recomple... yet everything STILL continues to run fine, and I'm on 6-CURRENT now.
I DID recompile all C++ apps (because of the ABI change with the compiler upgrade) and all threaded apps (just because I didn't want a libmap.conf).
I'll agree that it's best to recompile all C++ and threaded apps, but it's not necessary to recompile everything.
You're right about the RANDOM_IP_ID one, but that's the only one I've come across that has given me problems.
Actually, you don't have to recompile ALL your ports... just the C++ ones that stop running after you upgrade. The threading lib upgrades don't change the ABI so those don't have to be recompiled. In short, it's not "painless" but it's not as painful as you make it out to be... Oh, and I don't know about anything that got turned into a sysctl from a kernel option, but I know that you have to add a couple of kernel options (or modules) to your kernel to get the same functionality... I believe there is io.ko and mem.ko to get/dev/io and/dev/mem.
Actually no, REM sleep is when you dream, and it's the lightest sleep. Ever woke up from a dream where you heard a noise in your dream, and when you wake up you find that the noise is real and it's a bird making weird squawking noises?
Aside from that you're right though, if you wake up from a dream you'll usually feel better than if you wake up from deep (dreamless) sleep.
My vision is great after the surgery, 20/15, and I can see close up really well too, but...
My vision wasn't that bad to begin with, 20/100, and I had some problems, and am still having some problems. They cut a flap in your cornea and laser underneath it, then put the flap back, but there's not really anything to hold it in place, and that's fine for most people, but for me, my left eye flap came loose 4 days in a row after the surgery, before it finally stayed put. Then later, my right eye started getting "surface cells" growing underneath the flap, so I'm going monday to have those cleaned out... which means my recovery for that eye is basically starting over. I originally had the surgery on Dec 1, 2003, so it's a big start-over.
All that said, I'm glad I did it, and when it's fixed on monday, I'm pretty sure all will be fine after that.
ACTUALLY, I just read it... in some cases the rebuttal is scientific, but in others, the evidence is just as circumstantial as Hoagland's. And in my opinion we won't know the answer to some of the claim until someone goes there and looks.
In the DEVICE_POLLING part of the article, he says setting HZ=1000 in the kernel config slows town the clock, but that's wrong... it speeds it up... it ticks ever 1 ms instead of FreeBSD's default ever 10 ms. Last I checked that was speeding up not slowing down.
Ok, I'll admit I shouldn't have called you names, but this kind of kneejerk reaction should be expected when you don't even look on netcraft or anywhere else to verify what you say.
Like I said before... you are a moron. You think the slashdot crowd knows anything? Most of them are a bunch of Linux Fanboyz who know nothing about how the os works.
With that out of the way, Several production shops use FreeBSD on their servers. Yahoo, Sony japan, Hotmail (yes, they still do, even if they won't admit it). And another thing, I was looking at linux's so-called SMP support the other day, (mainly because netstat was hanging for like 1.6 seconds on my 2.4 kernel 4 way smp machines) and the locking is horrible. Just running a netstat causes the rest of the TCP system to hang while the netstat completes. And it's noticable, The webserver latency goes from 5 ms to 1.9 seconds.
Things like this are why FreeBSD is still used anywhere that needs to support high traffic and high uptime.
you are a moron. Think yahoo, sony japan, hell even hotmail still has bsd boxes. Not to mention just about every hosting service that actually stays up for any amount of time is running on FreeBSD, and netcraft shows that the machines with the highest uptime are all BSD. Go back into the hole you crawled out of.
You didn't read very carefully, The DRI driver will NOT work for anything over lower 9000's radeons. It won't work for 9500 or above. That means no 3d if you have a modern card.
Chances are for his XFree86 problems, XFree86 4.3.0 as far as I know has a driver for Xfree86, and if it doesn't, it's not that hard to get at least accelerated 2d working. It involves compiling Xfree86 from CVS, which isn't hard at all. His kernel config file has several options in it which WILL slow down his system significantly. His problems with the mailing list are expected, mainly because the questions he's asked have been answered several times in several places.
This quote is true though "The initial learning curve can be discouraging, but once you learn and get used to FreeBSD, all other operating systems seem slow, weak and brittle."
most mp3 players DO support wma, or if they don't, can be made to via a simple firmware update
Re:Even Apple knew enough to change
on
Support FreeBSD
·
· Score: 2, Interesting
I disagree, tcsh is a great shell, normal csh sucks. Which shell you use is largely personal preference, but in my eyes, tcsh and bash are equal in terms of features, so after that just use the shell you prefer. I personally prefer tcsh, as do many of the people who use FreeBSD.
I don't think I'd want this. This would SUCK in a sports car where you actually WANT to be driving fast and in complete control of your vehicle. Just think when your drafting someone and all the sudden the car hits the brakes for you, then you lose the race. That would suck. I'm kinda disappointed in all these "new technologies" taking more and more control away from the driver.
Are you people who are seeing all these hard drive failures actually keeping the drives cool enough? My drives run around 28-30C and I've never had a problem with ANY of them. BOTH of them are 7200 RPM 8MB Cache Maxtors right now, but all my previous drives have been maxtors as well and I've never had a problem.
Basically I'm anal about keeping the case cool so I have lots of fans (with a fan controller so I can sleep with the computer on) but my drives always have a lot of airflow over them.
I'm using a 9700 pro (the open source 2d support) on FreeBSD with XFree86 4.3.0, and I see no problems at all... I mean other than the obvious that I can't play 3d games.
This sounds like very good news for AMD, and sounds like they'll have a lot more acceptance for x86-64 than most people originally thought. Either way I'm happy to see this because the more competition the better
FreeBSD has linux threads which do something similar.... FreeBSD 5.0-RELEASE (as far as I know) will also have it's own form of kernel threading called KSE's... These are much better than the rfork threads.
Well, I actually compiled it on FreeBSD, but due to some linux-isms that I didn't bother porting properly and just wanted to see if it would compile (or better yet run anything). The version I managed to compile on FreeBSD wouldn't run anything, so that's why I went ahead and plunked down my $5 per month and got wc3 working on FreeBSD:-)
Slashdot Mirror
The dealer is not going to be equipped in most cases to deal with what looks like a software problem unless the software problem has already been resolved with a firmware update.
They can't rewrite the software, they can only load new firmware provided by the engineers.
I just made the switch to FiOS... I'm pretty happy with it.
So far, it's been like dealing with a totally different company when dealing with anything related to FiOS. They show none of their old nickel-and-diming that they did on the normal phone service, and they have been very responsive.
Not only that, when they got to my house, we didn't have a fiber drop to the house (it was at the end of the block), so the tech called his boss, who sent a truck full of people to dig the trench and run the line the rest of the way to the house (across several neighbors' yards). When they were done they cleaned it all up so well you wouldn't even know they had been there.
The combined install time for Cable and Fiber was about 6 hours I think, but I wasn't there for the whole thing.
I've been running -CURRENT since before the libpthread integration, and I still have apps that I've been too lazy to recomple... yet everything STILL continues to run fine, and I'm on 6-CURRENT now.
I DID recompile all C++ apps (because of the ABI change with the compiler upgrade) and all threaded apps (just because I didn't want a libmap.conf).
I'll agree that it's best to recompile all C++ and threaded apps, but it's not necessary to recompile everything.
You're right about the RANDOM_IP_ID one, but that's the only one I've come across that has given me problems.
Actually, you don't have to recompile ALL your ports... just the C++ ones that stop running after you upgrade. The threading lib upgrades don't change the ABI so those don't have to be recompiled. In short, it's not "painless" but it's not as painful as you make it out to be... Oh, and I don't know about anything that got turned into a sysctl from a kernel option, but I know that you have to add a couple of kernel options (or modules) to your kernel to get the same functionality... I believe there is io.ko and mem.ko to get /dev/io and /dev/mem.
Actually no, REM sleep is when you dream, and it's the lightest sleep. Ever woke up from a dream where you heard a noise in your dream, and when you wake up you find that the noise is real and it's a bird making weird squawking noises?
Aside from that you're right though, if you wake up from a dream you'll usually feel better than if you wake up from deep (dreamless) sleep.
My vision is great after the surgery, 20/15, and I can see close up really well too, but...
My vision wasn't that bad to begin with, 20/100, and I had some problems, and am still having some problems. They cut a flap in your cornea and laser underneath it, then put the flap back, but there's not really anything to hold it in place, and that's fine for most people, but for me, my left eye flap came loose 4 days in a row after the surgery, before it finally stayed put. Then later, my right eye started getting "surface cells" growing underneath the flap, so I'm going monday to have those cleaned out... which means my recovery for that eye is basically starting over. I originally had the surgery on Dec 1, 2003, so it's a big start-over.
All that said, I'm glad I did it, and when it's fixed on monday, I'm pretty sure all will be fine after that.
ACTUALLY, I just read it... in some cases the rebuttal is scientific, but in others, the evidence is just as circumstantial as Hoagland's. And in my opinion we won't know the answer to some of the claim until someone goes there and looks.
I read the CNN article, and that was mostly handwaving and attacking of credibility.
yeah, kinda funny isn't it? Neither of them use actual science.
oops, forgot to say... take it for what its worth, who knows what's true and what's not.
Actually, the claims aren't really debunked, instead, Plait attacks Hoaglands credibility.
Oh, and this article is old, there's already a rebuttal over at Enterprisemission
In the DEVICE_POLLING part of the article, he says setting HZ=1000 in the kernel config slows town the clock, but that's wrong... it speeds it up... it ticks ever 1 ms instead of FreeBSD's default ever 10 ms. Last I checked that was speeding up not slowing down.
Ok, I'll admit I shouldn't have called you names, but this kind of kneejerk reaction should be expected when you don't even look on netcraft or anywhere else to verify what you say.
Like I said before... you are a moron. You think the slashdot crowd knows anything? Most of them are a bunch of Linux Fanboyz who know nothing about how the os works.
With that out of the way, Several production shops use FreeBSD on their servers. Yahoo, Sony japan, Hotmail (yes, they still do, even if they won't admit it). And another thing, I was looking at linux's so-called SMP support the other day, (mainly because netstat was hanging for like 1.6 seconds on my 2.4 kernel 4 way smp machines) and the locking is horrible. Just running a netstat causes the rest of the TCP system to hang while the netstat completes. And it's noticable, The webserver latency goes from 5 ms to 1.9 seconds.
Things like this are why FreeBSD is still used anywhere that needs to support high traffic and high uptime.
you are a moron. Think yahoo, sony japan, hell even hotmail still has bsd boxes. Not to mention just about every hosting service that actually stays up for any amount of time is running on FreeBSD, and netcraft shows that the machines with the highest uptime are all BSD. Go back into the hole you crawled out of.
You didn't read very carefully, The DRI driver will NOT work for anything over lower 9000's radeons. It won't work for 9500 or above. That means no 3d if you have a modern card.
Chances are for his XFree86 problems, XFree86 4.3.0 as far as I know has a driver for Xfree86, and if it doesn't, it's not that hard to get at least accelerated 2d working. It involves compiling Xfree86 from CVS, which isn't hard at all. His kernel config file has several options in it which WILL slow down his system significantly. His problems with the mailing list are expected, mainly because the questions he's asked have been answered several times in several places.
This quote is true though "The initial learning curve can be discouraging, but once you learn and get used to FreeBSD, all other operating systems seem slow, weak and brittle."
Definitely true.
most mp3 players DO support wma, or if they don't, can be made to via a simple firmware update
I disagree, tcsh is a great shell, normal csh sucks. Which shell you use is largely personal preference, but in my eyes, tcsh and bash are equal in terms of features, so after that just use the shell you prefer. I personally prefer tcsh, as do many of the people who use FreeBSD.
I don't think I'd want this. This would SUCK in a sports car where you actually WANT to be driving fast and in complete control of your vehicle. Just think when your drafting someone and all the sudden the car hits the brakes for you, then you lose the race. That would suck. I'm kinda disappointed in all these "new technologies" taking more and more control away from the driver.
Are you people who are seeing all these hard drive failures actually keeping the drives cool enough? My drives run around 28-30C and I've never had a problem with ANY of them. BOTH of them are 7200 RPM 8MB Cache Maxtors right now, but all my previous drives have been maxtors as well and I've never had a problem.
Basically I'm anal about keeping the case cool so I have lots of fans (with a fan controller so I can sleep with the computer on) but my drives always have a lot of airflow over them.
I'm using a 9700 pro (the open source 2d support) on FreeBSD with XFree86 4.3.0, and I see no problems at all... I mean other than the obvious that I can't play 3d games.
This sounds like very good news for AMD, and sounds like they'll have a lot more acceptance for x86-64 than most people originally thought. Either way I'm happy to see this because the more competition the better
FreeBSD has linux threads which do something similar.... FreeBSD 5.0-RELEASE (as far as I know) will also have it's own form of kernel threading called KSE's... These are much better than the rfork threads.
Well, I actually compiled it on FreeBSD, but due to some linux-isms that I didn't bother porting properly and just wanted to see if it would compile (or better yet run anything). The version I managed to compile on FreeBSD wouldn't run anything, so that's why I went ahead and plunked down my $5 per month and got wc3 working on FreeBSD :-)