The file should not handle it directly. If you do, a reformat destroys all of the wear-levelling data.
And something akin to SMART but with added retention of how many times each sector has been written to is an issue how? would stay persistent even with formats and would help the OS determine the best places to write also.
The file system does not handle it directly.
If you use windows then yes.. but more accurately what I should have said is that the drives should allow you to access them in raw mode, hell even default to wear leveling in the controller if you want.. but allow us to disable it when we are using something good enough to do better.
the only reason they are using controller wear-leveling in the first place is that the popular operating systems of the time did not do so themselves
really the drive knows nothing about the filesystem and how it wants to store it's data, let the os decide how to wear level, it knows more and can make more informed decisions.. seriously the only reason I don't have an SSD drive already is this hardware wear-leveling crap which is a completely unsuitable way of fixing things.
Intel once thought VLIW was the future also, thusly making the Itanium IA64 architecture.. and I'm sure you'd know how that turned out for them.
For VLIW to be properly used compilers would have to significantly improved for the scheduling of out of order instructions at compile time.
that being said I still need to pick up an IA64 system, it's one of the last remaining on my to get list (have superhitachi, 68k, arm, ppc, sparc, mips, etc etc)
don't know about you, but for me VI on a p3 450 from 1999 goes faster than the blink of an eye when editing text, no waiting for it at all.
For a given usage people don't need faster computers.. (ok except 3d rendering and other infinite processing time things) it's just the usage patterns change and developers misusing abundant resources (flash web pages that make core2duos crawl anyone?)
depends what you are doing really, for mainstream things the only thing I've found that does that are non-mainline kernel modules that haven't been updated because of interface changes. GCC is also a moving target.. the changes are always ever so slight, but an ever so slight change is all that is needed for some trivial break.
I'm on the board of one project that's offering Internet access over HF radio
Dude.. I've done that before also, are you bouncing it off the ionosphere to get it there? what kind of modulation techniques are you using? phase shift keying or something else.? with the severe limitations you encounter with HF it's hard to get reliable connections over like 2400 baud. Even with the tiny download sizes of things in plaintext (and compression) 100kb files would still take ages.
being the owner of a nokia n95 (s60 symbian) I am puzzled at how you can not run your own code.. when running unsigned code it just tells me "warning: blah is not signed" just like ssh warns me when a key is changed or some such. Then I can install it anyway.
I have not yet found any kind of drm in the phone.. at all. I install what I like from wherever I like and it just works.
The rest of your post can be summaried as "it's different from unix, so I don't like it" which is your opinion to have, but it is an opinion. I agree having everything be like linux/bsd etc would make life as a developer a lot easier, nothing new to learn.
If 9,999 people on a FOSS project are not sexist... but 1 person is... how does that 1 person contaminate the other 9,999?
When the other 9,999 don't acknowledge or reject the sexism of the 1.
Half of the problems with the feminist movement are the extremists that call absolutely everything sexist.. because of that people are desensitized when someone calls something sexist, only concrete examples which people can analyze for themselves as sexist will prove to them that it actually went on.
Sex is irrelevent in the oss world, I mean hell, if you hadn't of mentioned it, I wouldn't have even known you were a woman. People are judged by their merits and by the merits of their code. Harsh quality standards mean even the best of us get patches rejected fairly frequently.
I've seen women that consider that just being a male, makes you a 'rapist' and were concerned when they had a baby boy that one day they would be one, just because they were male. Does every female have to acknowledge the sexism of that? not really I trust the rest of them are mostly more sane.
When someone wrongs you, the best thing is to present evidence and your argument to people in that specific instance, just calling it without that makes people skeptical.
Any references on this? I've been a fedora user since it was redhat 6, and I see no reason to drop perfectly good hardware. I'm still using my 32-bit p4 from 2003
If you've noticed, with x86 the number of bits in the registers and addressable memory only ever seems to increase when it starts to become cheap enough that more memory can be easily bought than can be addressed.
And each time it takes more time to fully use the new addressable memory size, since it is to much larger. it will take at least 20 years before we start using the 64-bit memory addresses to their fullest.. even assuming that ram doubles in size every year.
In the end I guess, I know anything I write will infringe patents to some extent, so I don't care what I code for, I fix problems with code. To be told I cannot write what I want seems extremely.. limiting and unfree. Such is the world of software patents of course, but if I'm fucked either way I'd rather implement things however I like without even looking at patents. Stupidity be damned.
Just as people are free to write proprietary software, people should be allowed to write things with mono, it's their choice.
"We are not here to give users what they want, we are here to spread freedom" - Richard Stallman
The freedom he speaks of in the software patents aspect is very twisted, since patents inherently limit peoples ability to do what they want the way they want with their software.
I'd rather ignore all software patents, and take my chances fighting them than limit what I write. Even if mono WAS successfully sued, do you really think it would cease development or disappear? Just as I'm sure the open implementations of decoders for patented codecs magically don't exist any more.
Personally, I don't even like.net much at all, but I respect peoples freedom to use software they've written themselves, no matter what it implements. I know under the current system this can be illegal depending on functionality/country of residence (dmca and all that)
You have to admit though, Stallman is hardline no grey area, if you can point at a specific patent for a piece of software, he will call it the devil and not free, even if the party has no intention on sueing for damages/royalties. This almost makes me actually want to go patent hunting, if it wasn't for the fact I love OSS software.
I agree with stallmans views on 99% of things, but with certain items such as this he's just too hardcore, with enough vague unknown patents you could make almost all OSS illegal if everyone was hardline 'no patents allowed' and stuck to it.
In sticking with the fat example.. it was KNOWN that linux violated the fat long filename support patent for quite some time.. but it was only changed when microsoft sued tom tom.. why? if the mere danger of the patent existing is enough shouldn't it have been re-written long before that and never been an issue?
Anyways, I tire of this, to some people RMS can do no wrong, I applaud most of his efforts, but remain that as an end user and as a developer, it's MY CHOICE what software I want to run. Being "no patents or die" ensures that anyone with a patent vague enough can take chunks out of OSS
I do apologise for not backing up my arguments earlier more though with references, hunting through patents really isn't the highlight of my day
Yeah except that's not RMS' "lines". He's not against interoperability or compatibility.
Of course not, but he is against anything whatsoever covered by patents.. which is basically any standard ever made by microsoft.
Wine doesn't implement any patented technology -- if it did, it would be a ridiculously easy target.
It IS a ridiculously easy target.. that has not been attacked yet.
Samba is similar. That's actually a project RMS loves, because it undoes proprietary lock in. They didn't implement anything patented. And when they had to in order to get all of the functionality, they did so under an agreement [samba.org]
Ah so it does implement things covered by patents now, but has an agreement? just like mono has a free use of patents agreement with microsoft for the ecma standard... so difference please?
Yeah, because there aren't any non-proprietary non-encumbered file systems out there, FAT is it. *giant eyeroll*
Please don't make me pull out trivial patents that effect other parts of the kernel, significant proportions of wifi code would have to be removed due to CSIRO wifi patents, etc.. without the patented parts the whole stack is useless.
Chances are even ext3 infringes some patent if you look deep enough. The point, however is that people only seem to give a crap about this since it's both microsoft and non-native code.
If you take "potentially" to mean "realistically" rather than merely "hypothetically", then there would be plenty left. Like... just about everything in a modern distro. There were "realistic" patent problems with writing.gifs.
So what you are saying is we should wait until we are actually getting sued to remove that functionality, I completely agree, however microsoft has not sued yet, people are just fearing it like the plague.
Surprisingly, mono helps stop lock-in also, the sims 3 was written entirely in.net, and since mono is mostly there, was playable on release day on linux thanks to it. There are other instances of course.
While I don't code in mono except when I have to for some projects, I also fail to see why people decry mono so much and yet are accepting of samba and wine. Considering the only reason they are so negative is because of patents, one would think they would hate all of the projects.
If you consider mono microsoft controlled software... what about wine? samba? openoffice (since they implement ooxml compat) since all of these things more than likely have some form of software patent associated with them.
If all patent encumbered software was removed from a typical linux distro.. you'd have no dvd playback still, you couldn't mount fat filesystems, etc... almost everything you can think of in software infringes a patent if you look hard enough for one
What is even more strange, is that people shun mono so harshly, but go "YAY!" when wine version blah is released. When both have nothing to do with microsoft except in that they implement compatibility for something microsoft initially designed.
If you follow RMS's lines, the mpeg group is just as evil because they have patents on their codecs.. wine should be completely banned, and hell, even openoffice implements a 'standard' made by microsoft in the name of compatibility (mono implements.net ecma standard also)
Samba would also have to go too, and the list goes on. All of these projects were made completely independently by enthusiasts that just wanted to make things for compatibility sake
If every potentially patent encumbered item were removed from a linux distro, there wouldn't be anything left, even ancient things like fat drivers still have some patent litigation around them.
While microsoft has trumped up lots of fud.. they really have had no effect on the actual business of the free software world.
This almost non-sensical fear of mono seems strange to me.. I consider it like wine, avoid relying on it if possible since native is better, but if you need it it's there and it's free software. The ONLY way you could consider it non-free software is if you count anything that could possibly infringe patents... which is a fair majority of gpl apps if you look through enough patents.
Today we can only try to anticipate what it will do, based on its statements and Microsoft's statements.
It's all conjecture, the entire basis of his attack is that it could be bad because it's heavily influenced by microsoft. I don't trust microsoft as much as the next person, but get them for what they DO do (while safeguarding yourself from harm), as opposed to what they could potentially do, with their own platform.
The people that are making this initiative have every right to do what they want with their own code.
Slashdot Mirror
The file should not handle it directly. If you do, a reformat destroys all of the wear-levelling data.
And something akin to SMART but with added retention of how many times each sector has been written to is an issue how? would stay persistent even with formats and would help the OS determine the best places to write also.
The file system does not handle it directly.
If you use windows then yes.. but more accurately what I should have said is that the drives should allow you to access them in raw mode, hell even default to wear leveling in the controller if you want.. but allow us to disable it when we are using something good enough to do better.
the only reason they are using controller wear-leveling in the first place is that the popular operating systems of the time did not do so themselves
really the drive knows nothing about the filesystem and how it wants to store it's data, let the os decide how to wear level, it knows more and can make more informed decisions.. seriously the only reason I don't have an SSD drive already is this hardware wear-leveling crap which is a completely unsuitable way of fixing things.
decent price, nice bonus with the jtag adapter too, I still have a ghetto one I made for parallel port when I was playing with cpld's.
Intel once thought VLIW was the future also, thusly making the Itanium IA64 architecture.. and I'm sure you'd know how that turned out for them.
For VLIW to be properly used compilers would have to significantly improved for the scheduling of out of order instructions at compile time.
that being said I still need to pick up an IA64 system, it's one of the last remaining on my to get list (have superhitachi, 68k, arm, ppc, sparc, mips, etc etc)
don't know about you, but for me VI on a p3 450 from 1999 goes faster than the blink of an eye when editing text, no waiting for it at all.
For a given usage people don't need faster computers.. (ok except 3d rendering and other infinite processing time things) it's just the usage patterns change and developers misusing abundant resources (flash web pages that make core2duos crawl anyone?)
how much did it cost you? been looking at getting one myself.
Try making a model for adult size hands. Better yet, adult sized Western or European/American hands...
They did.. the original model. while the DS lite had a much better screen, the controls became horrid.
depends what you are doing really, for mainstream things the only thing I've found that does that are non-mainline kernel modules that haven't been updated because of interface changes. GCC is also a moving target.. the changes are always ever so slight, but an ever so slight change is all that is needed for some trivial break.
I'm on the board of one project that's offering Internet access over HF radio
Dude.. I've done that before also, are you bouncing it off the ionosphere to get it there? what kind of modulation techniques are you using? phase shift keying or something else.? with the severe limitations you encounter with HF it's hard to get reliable connections over like 2400 baud. Even with the tiny download sizes of things in plaintext (and compression) 100kb files would still take ages.
being the owner of a nokia n95 (s60 symbian) I am puzzled at how you can not run your own code.. when running unsigned code it just tells me "warning: blah is not signed" just like ssh warns me when a key is changed or some such. Then I can install it anyway.
I have not yet found any kind of drm in the phone.. at all. I install what I like from wherever I like and it just works.
The rest of your post can be summaried as "it's different from unix, so I don't like it" which is your opinion to have, but it is an opinion. I agree having everything be like linux/bsd etc would make life as a developer a lot easier, nothing new to learn.
They have better hardware designers.
Citation needed. the iphone may be a great pda, but it's shite as an actual phone. No tactile feedback, screen prone to getting smashed, etc
How about all those SunRays you've got in the garage?
The SunRays are sitting on top of my sun enterprise rack in my room, you insensitive clod! (not kidding, behind me to my right :) )
Indeed, the quality between cd vs vinyl is slightly arguable (in weather you can hear it). The difference between cd and shitty mp3's etc is not.
If 9,999 people on a FOSS project are not sexist ... but 1 person is ... how does that 1 person contaminate the other 9,999?
When the other 9,999 don't acknowledge or reject the sexism of the 1.
Half of the problems with the feminist movement are the extremists that call absolutely everything sexist.. because of that people are desensitized when someone calls something sexist, only concrete examples which people can analyze for themselves as sexist will prove to them that it actually went on.
Sex is irrelevent in the oss world, I mean hell, if you hadn't of mentioned it, I wouldn't have even known you were a woman. People are judged by their merits and by the merits of their code. Harsh quality standards mean even the best of us get patches rejected fairly frequently.
I've seen women that consider that just being a male, makes you a 'rapist' and were concerned when they had a baby boy that one day they would be one, just because they were male. Does every female have to acknowledge the sexism of that? not really I trust the rest of them are mostly more sane.
When someone wrongs you, the best thing is to present evidence and your argument to people in that specific instance, just calling it without that makes people skeptical.
Any references on this? I've been a fedora user since it was redhat 6, and I see no reason to drop perfectly good hardware. I'm still using my 32-bit p4 from 2003
If you've noticed, with x86 the number of bits in the registers and addressable memory only ever seems to increase when it starts to become cheap enough that more memory can be easily bought than can be addressed.
And each time it takes more time to fully use the new addressable memory size, since it is to much larger. it will take at least 20 years before we start using the 64-bit memory addresses to their fullest.. even assuming that ram doubles in size every year.
In the end I guess, I know anything I write will infringe patents to some extent, so I don't care what I code for, I fix problems with code. To be told I cannot write what I want seems extremely.. limiting and unfree. Such is the world of software patents of course, but if I'm fucked either way I'd rather implement things however I like without even looking at patents. Stupidity be damned.
Just as people are free to write proprietary software, people should be allowed to write things with mono, it's their choice.
"We are not here to give users what they want, we are here to spread freedom" - Richard Stallman
The freedom he speaks of in the software patents aspect is very twisted, since patents inherently limit peoples ability to do what they want the way they want with their software.
I'd rather ignore all software patents, and take my chances fighting them than limit what I write. Even if mono WAS successfully sued, do you really think it would cease development or disappear? Just as I'm sure the open implementations of decoders for patented codecs magically don't exist any more.
Personally, I don't even like .net much at all, but I respect peoples freedom to use software they've written themselves, no matter what it implements. I know under the current system this can be illegal depending on functionality/country of residence (dmca and all that)
You have to admit though, Stallman is hardline no grey area, if you can point at a specific patent for a piece of software, he will call it the devil and not free, even if the party has no intention on sueing for damages/royalties. This almost makes me actually want to go patent hunting, if it wasn't for the fact I love OSS software.
I agree with stallmans views on 99% of things, but with certain items such as this he's just too hardcore, with enough vague unknown patents you could make almost all OSS illegal if everyone was hardline 'no patents allowed' and stuck to it.
In sticking with the fat example.. it was KNOWN that linux violated the fat long filename support patent for quite some time.. but it was only changed when microsoft sued tom tom.. why? if the mere danger of the patent existing is enough shouldn't it have been re-written long before that and never been an issue?
Anyways, I tire of this, to some people RMS can do no wrong, I applaud most of his efforts, but remain that as an end user and as a developer, it's MY CHOICE what software I want to run. Being "no patents or die" ensures that anyone with a patent vague enough can take chunks out of OSS
I do apologise for not backing up my arguments earlier more though with references, hunting through patents really isn't the highlight of my day
Unlike GNU C, Linux, etc, which either implement published standards
.net has a published standard under ECMA something or other... that's what mono implements
Yeah except that's not RMS' "lines". He's not against interoperability or compatibility.
Of course not, but he is against anything whatsoever covered by patents.. which is basically any standard ever made by microsoft.
Wine doesn't implement any patented technology -- if it did, it would be a ridiculously easy target.
It IS a ridiculously easy target.. that has not been attacked yet.
Samba is similar. That's actually a project RMS loves, because it undoes proprietary lock in. They didn't implement anything patented. And when they had to in order to get all of the functionality, they did so under an agreement [samba.org]
Ah so it does implement things covered by patents now, but has an agreement? just like mono has a free use of patents agreement with microsoft for the ecma standard... so difference please?
Yeah, because there aren't any non-proprietary non-encumbered file systems out there, FAT is it. *giant eyeroll*
Please don't make me pull out trivial patents that effect other parts of the kernel, significant proportions of wifi code would have to be removed due to CSIRO wifi patents, etc.. without the patented parts the whole stack is useless.
Chances are even ext3 infringes some patent if you look deep enough. The point, however is that people only seem to give a crap about this since it's both microsoft and non-native code.
If you take "potentially" to mean "realistically" rather than merely "hypothetically", then there would be plenty left. Like... just about everything in a modern distro. There were "realistic" patent problems with writing .gifs.
So what you are saying is we should wait until we are actually getting sued to remove that functionality, I completely agree, however microsoft has not sued yet, people are just fearing it like the plague.
Surprisingly, mono helps stop lock-in also, the sims 3 was written entirely in .net, and since mono is mostly there, was playable on release day on linux thanks to it. There are other instances of course.
While I don't code in mono except when I have to for some projects, I also fail to see why people decry mono so much and yet are accepting of samba and wine. Considering the only reason they are so negative is because of patents, one would think they would hate all of the projects.
Microsoft controlled free software
If you consider mono microsoft controlled software... what about wine? samba? openoffice (since they implement ooxml compat) since all of these things more than likely have some form of software patent associated with them.
If all patent encumbered software was removed from a typical linux distro.. you'd have no dvd playback still, you couldn't mount fat filesystems, etc... almost everything you can think of in software infringes a patent if you look hard enough for one
What is even more strange, is that people shun mono so harshly, but go "YAY!" when wine version blah is released. When both have nothing to do with microsoft except in that they implement compatibility for something microsoft initially designed.
If you follow RMS's lines, the mpeg group is just as evil because they have patents on their codecs.. wine should be completely banned, and hell, even openoffice implements a 'standard' made by microsoft in the name of compatibility (mono implements .net ecma standard also)
Samba would also have to go too, and the list goes on. All of these projects were made completely independently by enthusiasts that just wanted to make things for compatibility sake
If every potentially patent encumbered item were removed from a linux distro, there wouldn't be anything left, even ancient things like fat drivers still have some patent litigation around them.
While microsoft has trumped up lots of fud.. they really have had no effect on the actual business of the free software world.
This almost non-sensical fear of mono seems strange to me.. I consider it like wine, avoid relying on it if possible since native is better, but if you need it it's there and it's free software. The ONLY way you could consider it non-free software is if you count anything that could possibly infringe patents... which is a fair majority of gpl apps if you look through enough patents.
Today we can only try to anticipate what it will do, based on its statements and Microsoft's statements.
It's all conjecture, the entire basis of his attack is that it could be bad because it's heavily influenced by microsoft. I don't trust microsoft as much as the next person, but get them for what they DO do (while safeguarding yourself from harm), as opposed to what they could potentially do, with their own platform.
The people that are making this initiative have every right to do what they want with their own code.
When Nintendo releases DSi without previous gen games compatibility (unlike DS) it's the best hardware ever made.
Arguably the DSi does have support for previous gen games... ds games, as the ds had support for it's previous gen.. gba games.