Don't you listen to Rush Limbaugh? This is all part of evil plan set in motion by Bill Clinton and carried out by his minions. The Republican former FCC commissioner was a progressive sleeper agent.
There's no need to to recompile the kernel, it's a loadable module. Even more, mount_ntfs will autoload the module automatically if necessary from an fstab entry.
Additionally, there's no need to "enable write support". The limited writing ntfs.ko supports is always on provided you didn't do a read-only mount.
More mindless, ignorant bullshit. You can get a nice L1 charger that maybe weights in at all of 20 lbs. 20 minutes of charge would get you far enough to finish in a more convenient location. There are plenty of ways to get a depleted EV charged. For someone as smart as you, it's interesting you can only think of one method and that's the one that makes EV's seem totally unusable for real world activities.
There's also absolutely no other use for such a beast. Can of gas? Who doesn't have a can of gas. if you have a lawn, you have a lawn mower. If you have a lawn mower, YOU HAVE A CAN OF GAS.
Ohhh, you're an urbanite, no lawn mower, no can of gas? Sounds like a personal problem to me.
As a matter of fact, I'm anything but an urbanite. I live in quite a rural area, and frequently utilize gas cans for far more than just lawn mower usage. If you would bother to read what I said, I wrote "good gas". The problem with gas in gas cans is that it ages rapidly and frequently attracts water and sometimes more contamination. Some of my gas cans contain 2-stroke mixed fuel. I'm not about to allow gas out a gas can into my $30K car unless I've had the chain of custody on that gas/gas can the entire time.
What's the matter, you don't have simple extension cord? Where do you live?
Don't let your ignorance prevent you from continuing to post FUD.
There are portable(and some wireless) chargers for situations where an urgent charging is needed. About as fast and inconvenient as trying to scrounge up some proverbial gas can that's full of good gas just around the corner.
It is no more necessary to push an electric car than it is a liquid fueled one, unless of course you're going for the dramatic effect.
Um, no. Even my crush on Sandra could not salvage that movie. Glaring error after error. Not that I recognized these all live, but I may have blacked those parts out. One of the most regrettable two hour periods of my life.
Sure, it says right in the thread that when he reverted to default values the system was stable.
Anyways, there are some problem with uma(9) and ZFS so it's disabled by default.
It also seems that in 2GB systems, lots of hand tuning is required to avoid kernel panics but the Wiki is not kept up to date with the required information. Keeping up with the mailing list seems to be required.
The wiki has all the information you need to run stable regardless of RAM. For good understanding of performance, and other tunings participation in mailing lists and ongoing research is still a requirement. It's not like ZFS is perfect yet, there are still some corner cases where both performance and stability are affected(e.g. sendfile(2)). Hopefully everything will autotune at some point, but this type of in depth administration is actually pretty typical of introducing a new FS/features. For example, when softupdates first came to FreeBSD, it was a much more manual involved process and you could screw it up. The point is it if you adopt certain technology you are expected to know enough how to implement it. ZFS progress has been making it easier, but yes it's still more involved than a traditional file system.
A filesystem can't be considered 'stable' if it panics the kernel without a disastrous underlying hardware failure.
And ZFS doesn't do this if you follow the proper tuning. If you're an ext3/4 user, I hope you have barriers enabled.
The lists are full of corruption and panics with the ZFS+BSD stack.
Since I'm a member of every logical list one would seek out support for FreeBSD ZFS issues, I can assure you that there is not nearly the level of stability as you seem to believe. I've never had a single kernel panic or corrupted file due to ZFS in the nearly 2 years I've been using the setup, and that's including extensive "die mf, die" stress testing.
It's possible that they all have faulty SSD's that ignore write cache flushes, but it doesn't seem likely.
Yes faulty SSD's are not the lone culprit and that was shown in the thread I linked to as well. Other offenders are other types of flash media and some bad controllers. The offender I think is someone who has the skillset of the average Ubuntu user who's heard the ZFS and comes over to increase their geek cred. They go ahead and install ZFS on memory constraint i386 architectures. Then they hit the inevitable kernel panic and/or poor performance issues, blame FreeBSD and ZFS, take their ball and return to the mothership to relaying their poor experiences back to the Linux hive mind where is can be assimilated and disseminated. Problem is, documentation existed very early on and it's takes an almost active level of avoidance to not see it. This or similar user error are the bulk of the complaints in my estimation, not bad hardware. Of course, if you actually do have some evidence of corruption beyond hearsay and rumors, I would genuinely like to see it. I just don't think you can produce such evidence because I've been watching closely for a long time and haven't seen anything that would convincing point to FreeBSD as the likely cause of corruption.
CAIMLAS, do you never tired of trolling FreeBSD articles?
There is a binary upgrade path to both base system and ports. It takes approxiamately the same time to binary upgrade a Debian system as a FreeBSD one, except for certain ports which FreeBSD is not licensed to redistribute a binary form of the program. An example of this would be FreeBSD native JDK.
It's sorta sad you and others like you assume the ZFS corruption on FreeBSD is somehow FreeBSD's fault. I can provide examples of how ZFS pools/ZIL's can be corrupted regardless of the OS it's running under. (Hint: Lying hardware is to blame so it's neither OS or file system's responsibility)
I have no experience with that stuff, nor do I own some the components necessary to test. Were I to sing or preform musical compositions to my computer I believe it might cause some type of kernel panic or hardware failure. On the other hand, it would be hard for me to imagine that recording sound doesn't work. Audio support is generally very solid on FreeBSD for output at least. I know there are users doing things like skype and webcams. Webcams are a little trickier than recording audio though so I don't have a guess one way or the other on that one.
I don't print very much so I hadn't noticed the preview abilities absence in some of those apps. I imagine that would be an inconvenience if you are printing regularly from it. A couple other base KDE4 apps do have the ability and stuff like koffice does, and of course you can always print to a PDF/PS and open with okular and set it's format. Again, that would be an inconvenience but are you really trying to print from kate frequently? I use kate for many things, but not for printing. I can't even remember the last time I've printed code or a script on a piece of paper, but I'm sure it has to be a least several years. For documents that I do intend to print I use a word processor, and KDE4 based or not they seem to have a good print preview.
Looks like print preview is a relatively easy per-app setting in KDE4. I guess there hasn't been a lot of complaints, or it might have been fixed by now.
Yes you can get a accurate print preview with KDE4 apps, eg okular while printing to a CUPS based printer. I started using KDE4 full-time with the 4.2.x branch and I don't recall print preview as an issue. Maybe you were using some apps that hadn't been ported to correctly?
However... Its not as polished under the hood. At by that I simply mean kwin is much more finicky than metacity. I can crash kwin at will sometimes. When it does work, the display is less likely to be as smooth with or without the compositing. I'm looking forward to trying 4.6 as they say kwin's been fixed up quite a bit.
I think there's a decent chance you're citing problems with your OS's packages or some other external cause rather than a bonafide KDE4 problem. I've been running KDE4 build from FreeBSD ports for a couple years now, and 4.3+ has been exceptionally stable for me on issues like compositing/windowing and such. There are still a few quirks/bugs that I run into once in awhile, but they aren't anywhere near serious enough for me to consider switching DE's. I'd run KDE4 simply for konsole and it's notifications subsystem alone it's that useful to me.
I think a lot really depends on your platform and how/where/when you get the packages. Maybe year or so ago, I tried out KDE4 on a Debian Lenny install and it was an absolutely brutal experience. If I hadn't had a previous very solid experience with KDE4 on FreeBSD, I might have been tempted to assume it was a KDE4 issue. I've also seen some really awful versions of things like kubuntu which don't do anything to help KDE4 reputation.
Meteorology models were around before climatology models were.
Alchemy gave rise to chemistry so whatever your point was it's not founded on any sort of logic.
And accurate climatology models won't help meteorology predictions at all.
Complete BS. Climatology as a perfected science would include realtime models applicable to the micro-scale.
In some ways this is a semantics issue as given complete data and ability to process it, both sciences would result with the ability to do short and long term predictions. However as it stands now, meteorology is what happens when you can't see the forest from the trees.
The day climatologists perfect the science is the day meteorologists will be able to give forecasts with extraordinary accuracy. Meteorologists ride on the coattails of climatologists success.
On a massive public site, an unsigned certificate wouldn't be very comforting to the masses right? The CA for mail.google.com is: Thawte Consulting (Pty) Ltd.
Since the op's statement totally misses reality, I guess we're all even. Strict enforcement of current gun control laws would not have prevented or altered this event either.
Oh BS. This is just another endless troll of mankind. If you launch an investigation into the FSM stalking you, you'll end up with the exact same conclusion as the end of it and it would be whatever your bias was prior to entering the project.
This is just another form of intellectual masturbation except it's the supernatural that gets them off. If there was actual reproducible evidence to be found, you'd think one of the humans from any generation who was pursuing "spiritual enlightenment" would have come up with something solid by now.
I'm not saying you're wrong, but a link or some further evidence of micro-tornadoes would surely be in order.
I imagine someone coming across the frozen tundra and the corpse on it could easily reach a similar conclusion, even though the person may have died from some type of sudden onset failure like a brain aneurysm. Having been in northern climates, I'm having a bit of trouble swallowing these invisible micro tornadoes because much of the surface is covered with loose material like powder snow, dust, and exposed dry, decayed vegetation.
If you think a logical fallacy deserves a logical response as if the fallacy was an actual point point worth acknowledgment, then you've been watching too much Fox News. It does cause intellectual impairment, perhaps that explains the irrationality of your expectations.
Slashdot Mirror
Don't you listen to Rush Limbaugh? This is all part of evil plan set in motion by Bill Clinton and carried out by his minions. The Republican former FCC commissioner was a progressive sleeper agent.
Wrong.
http://www.undeadly.org/cgi?action=article&sid=20070829001634
There's no need to to recompile the kernel, it's a loadable module. Even more, mount_ntfs will autoload the module automatically if necessary from an fstab entry.
Additionally, there's no need to "enable write support". The limited writing ntfs.ko supports is always on provided you didn't do a read-only mount.
http://www.freebsd.org/cgi/man.cgi?query=mount_ntfs&sektion=8
Still hundreds of pounds.
More mindless, ignorant bullshit. You can get a nice L1 charger that maybe weights in at all of 20 lbs. 20 minutes of charge would get you far enough to finish in a more convenient location. There are plenty of ways to get a depleted EV charged. For someone as smart as you, it's interesting you can only think of one method and that's the one that makes EV's seem totally unusable for real world activities.
There's also absolutely no other use for such a beast. Can of gas? Who doesn't have a can of gas. if you have a lawn, you have a lawn mower. If you have a lawn mower, YOU HAVE A CAN OF GAS.
Ohhh, you're an urbanite, no lawn mower, no can of gas? Sounds like a personal problem to me.
As a matter of fact, I'm anything but an urbanite. I live in quite a rural area, and frequently utilize gas cans for far more than just lawn mower usage. If you would bother to read what I said, I wrote "good gas". The problem with gas in gas cans is that it ages rapidly and frequently attracts water and sometimes more contamination. Some of my gas cans contain 2-stroke mixed fuel. I'm not about to allow gas out a gas can into my $30K car unless I've had the chain of custody on that gas/gas can the entire time.
What's the matter, you don't have simple extension cord? Where do you live?
Don't let your ignorance prevent you from continuing to post FUD.
There are portable(and some wireless) chargers for situations where an urgent charging is needed. About as fast and inconvenient as trying to scrounge up some proverbial gas can that's full of good gas just around the corner.
It is no more necessary to push an electric car than it is a liquid fueled one, unless of course you're going for the dramatic effect.
How is that deceptive?
Do they push every car off the track to demonstrate what happens when fuel runs out?
I'd rather be a duct tape engineer than the guy complaining about them.
I thought that movie was fairly accurate.
Um, no. Even my crush on Sandra could not salvage that movie. Glaring error after error. Not that I recognized these all live, but I may have blacked those parts out. One of the most regrettable two hour periods of my life.
http://www.imdb.com/title/tt0113957/goofs
http://www.rottentomatoes.com/m/net/
My favorite review:
Low on both tension and credibility.
This is exactly what the FCC intended.
Perhaps you could illuminate that example?
Sure, it says right in the thread that when he reverted to default values the system was stable.
Anyways, there are some problem with uma(9) and ZFS so it's disabled by default.
It also seems that in 2GB systems, lots of hand tuning is required to avoid kernel panics but the Wiki is not kept up to date with the required information. Keeping up with the mailing list seems to be required.
The wiki has all the information you need to run stable regardless of RAM. For good understanding of performance, and other tunings participation in mailing lists and ongoing research is still a requirement. It's not like ZFS is perfect yet, there are still some corner cases where both performance and stability are affected(e.g. sendfile(2)). Hopefully everything will autotune at some point, but this type of in depth administration is actually pretty typical of introducing a new FS/features. For example, when softupdates first came to FreeBSD, it was a much more manual involved process and you could screw it up. The point is it if you adopt certain technology you are expected to know enough how to implement it. ZFS progress has been making it easier, but yes it's still more involved than a traditional file system.
A filesystem can't be considered 'stable' if it panics the kernel without a disastrous underlying hardware failure.
And ZFS doesn't do this if you follow the proper tuning. If you're an ext3/4 user, I hope you have barriers enabled.
The lists are full of corruption and panics with the ZFS+BSD stack.
Since I'm a member of every logical list one would seek out support for FreeBSD ZFS issues, I can assure you that there is not nearly the level of stability as you seem to believe. I've never had a single kernel panic or corrupted file due to ZFS in the nearly 2 years I've been using the setup, and that's including extensive "die mf, die" stress testing.
It's possible that they all have faulty SSD's that ignore write cache flushes, but it doesn't seem likely.
Yes faulty SSD's are not the lone culprit and that was shown in the thread I linked to as well. Other offenders are other types of flash media and some bad controllers. The offender I think is someone who has the skillset of the average Ubuntu user who's heard the ZFS and comes over to increase their geek cred. They go ahead and install ZFS on memory constraint i386 architectures. Then they hit the inevitable kernel panic and/or poor performance issues, blame FreeBSD and ZFS, take their ball and return to the mothership to relaying their poor experiences back to the Linux hive mind where is can be assimilated and disseminated. Problem is, documentation existed very early on and it's takes an almost active level of avoidance to not see it. This or similar user error are the bulk of the complaints in my estimation, not bad hardware. Of course, if you actually do have some evidence of corruption beyond hearsay and rumors, I would genuinely like to see it. I just don't think you can produce such evidence because I've been watching closely for a long time and haven't seen anything that would convincing point to FreeBSD as the likely cause of corruption.
CAIMLAS, do you never tired of trolling FreeBSD articles?
There is a binary upgrade path to both base system and ports. It takes approxiamately the same time to binary upgrade a Debian system as a FreeBSD one, except for certain ports which FreeBSD is not licensed to redistribute a binary form of the program. An example of this would be FreeBSD native JDK.
It's sorta sad you and others like you assume the ZFS corruption on FreeBSD is somehow FreeBSD's fault. I can provide examples of how ZFS pools/ZIL's can be corrupted regardless of the OS it's running under. (Hint: Lying hardware is to blame so it's neither OS or file system's responsibility)
http://mail.opensolaris.org/pipermail/zfs-discuss/2010-January/035740.html -- After digging into a few ZFS corruption complaints on FreeBSD, this type of error seems to be the most common one.
Can you demonstrate a scenario where FreeBSD is the cause of ZFS corruption?
I have no experience with that stuff, nor do I own some the components necessary to test. Were I to sing or preform musical compositions to my computer I believe it might cause some type of kernel panic or hardware failure. On the other hand, it would be hard for me to imagine that recording sound doesn't work. Audio support is generally very solid on FreeBSD for output at least. I know there are users doing things like skype and webcams. Webcams are a little trickier than recording audio though so I don't have a guess one way or the other on that one.
This is the most recent update on that end.
http://www.freebsd.org/news/status/report-2010-10-2010-12.html#Webcamd
I don't print very much so I hadn't noticed the preview abilities absence in some of those apps. I imagine that would be an inconvenience if you are printing regularly from it. A couple other base KDE4 apps do have the ability and stuff like koffice does, and of course you can always print to a PDF/PS and open with okular and set it's format. Again, that would be an inconvenience but are you really trying to print from kate frequently? I use kate for many things, but not for printing. I can't even remember the last time I've printed code or a script on a piece of paper, but I'm sure it has to be a least several years. For documents that I do intend to print I use a word processor, and KDE4 based or not they seem to have a good print preview.
Looks like print preview is a relatively easy per-app setting in KDE4. I guess there hasn't been a lot of complaints, or it might have been fixed by now.
https://bugs.kde.org/show_bug.cgi?id=177542
Yes you can get a accurate print preview with KDE4 apps, eg okular while printing to a CUPS based printer. I started using KDE4 full-time with the 4.2.x branch and I don't recall print preview as an issue. Maybe you were using some apps that hadn't been ported to correctly?
However ... Its not as polished under the hood. At by that I simply mean kwin is much more finicky than metacity. I can crash kwin at will sometimes. When it does work, the display is less likely to be as smooth with or without the compositing. I'm looking forward to trying 4.6 as they say kwin's been fixed up quite a bit.
I think there's a decent chance you're citing problems with your OS's packages or some other external cause rather than a bonafide KDE4 problem. I've been running KDE4 build from FreeBSD ports for a couple years now, and 4.3+ has been exceptionally stable for me on issues like compositing/windowing and such. There are still a few quirks/bugs that I run into once in awhile, but they aren't anywhere near serious enough for me to consider switching DE's. I'd run KDE4 simply for konsole and it's notifications subsystem alone it's that useful to me.
I think a lot really depends on your platform and how/where/when you get the packages. Maybe year or so ago, I tried out KDE4 on a Debian Lenny install and it was an absolutely brutal experience. If I hadn't had a previous very solid experience with KDE4 on FreeBSD, I might have been tempted to assume it was a KDE4 issue. I've also seen some really awful versions of things like kubuntu which don't do anything to help KDE4 reputation.
Meteorology models were around before climatology models were.
Alchemy gave rise to chemistry so whatever your point was it's not founded on any sort of logic.
And accurate climatology models won't help meteorology predictions at all.
Complete BS. Climatology as a perfected science would include realtime models applicable to the micro-scale.
In some ways this is a semantics issue as given complete data and ability to process it, both sciences would result with the ability to do short and long term predictions. However as it stands now, meteorology is what happens when you can't see the forest from the trees.
The day climatologists perfect the science is the day meteorologists will be able to give forecasts with extraordinary accuracy. Meteorologists ride on the coattails of climatologists success.
(Does anyone really sign Google's certificates?).
On a massive public site, an unsigned certificate wouldn't be very comforting to the masses right?
The CA for mail.google.com is:
Thawte Consulting (Pty) Ltd.
Since the op's statement totally misses reality, I guess we're all even. Strict enforcement of current gun control laws would not have prevented or altered this event either.
Oh BS. This is just another endless troll of mankind. If you launch an investigation into the FSM stalking you, you'll end up with the exact same conclusion as the end of it and it would be whatever your bias was prior to entering the project.
This is just another form of intellectual masturbation except it's the supernatural that gets them off. If there was actual reproducible evidence to be found, you'd think one of the humans from any generation who was pursuing "spiritual enlightenment" would have come up with something solid by now.
I'm not saying you're wrong, but a link or some further evidence of micro-tornadoes would surely be in order.
I imagine someone coming across the frozen tundra and the corpse on it could easily reach a similar conclusion, even though the person may have died from some type of sudden onset failure like a brain aneurysm. Having been in northern climates, I'm having a bit of trouble swallowing these invisible micro tornadoes because much of the surface is covered with loose material like powder snow, dust, and exposed dry, decayed vegetation.
If you think a logical fallacy deserves a logical response as if the fallacy was an actual point point worth acknowledgment, then you've been watching too much Fox News. It does cause intellectual impairment, perhaps that explains the irrationality of your expectations.
Best red herring I've seen today!