the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Luigi GenoniQuoted 13 lines · Luigi Genoni
Quoted 8 lines · Adrian Bunk
Quoted 4 lines
Said that pretending that KLive data has absolutely no significance at all and that you can't draw any conclusion at all from it, to me seems as wrong as pretending it to perfect.
Possibly wrong conclusions about the general market share based on data not having the quality for being the basis of such statements are worse than having no data.
Quoted 7 lines
Am I missing something, or it is not marketing what we are talking about? please I do not understand your point.
For what I understand... I was not supposing reiser4 users to be so mutch, but this is very usefull because this means that there are more possibilities to test the code well and to fix bugs...
...
I'm sorry for saying it that directly, and this is not meant against you personally:
Your statement is a good example why this data is worse than having no data.
As I already said in this thread:
<-- snip -->
You are able to say that based on klive data, reiser4 has at least 35 users in the world.
But you can not tell based on klive data whether the ratio of reiser4:ext3 users in the world is more like 1:5, 1:500 or 1:50000.
<-- snip -->
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data. But claiming it based on the klive data is worse since people like you are getting the wrong impression it was based on data that would have the quality for supporting such a statement.
The data simply has not the quality for such a statement. Please read my two examples in [1] if you want to get an impression why such problems can occur.
cu
Adrian
[1] http://lkml.org/lkml/2006/7/26/203
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Still I am missing something.
I am not interested in discussing about 1:5 ora 5:1 or so on.
I am not even interested if reiser4 users are 35 or 35000.
But if some people felt they need reiser4 to get their work done, that means something. The numbers and the datum per se are meaningless.
Anyway you have a datum.
Some people need reiser4, period.
Why they need reiser4?
all of them are just playing with him to have a new game for their spare time? I don't think so.
Some of them are using reiser4 because it is the best solution for their work? this is a concrete possibility.
again... why that?
Because the other FSs are not suitable for certain work? Because the other FSs are suitable, but reiser4 offers better results? Because even reiser4 is not complitelly suitable for some kind of work, but the other FSs are a worser solution?
I don't think most reiser4 users decided to give it a try just to enjoy their time making tests just because they are curious.
that does not mean reiser4 should be merged into linux kernel because of this. On the other side you can agree reiser4 has its place, because there are users who need it. What we would need to understand, sine ira nec studio, is where this place is.
Quoted 81 lines · Adrian Bunk
Quoted 14 lines · Luigi Genoni
Quoted 8 lines · Adrian Bunk
Quoted 4 lines
Said that pretending that KLive data has absolutely no significance at all and that you can't draw any conclusion at all from it, to me seems as wrong as pretending it to perfect.
Possibly wrong conclusions about the general market share based on data
not having the quality for being the basis of such statements are
worse than having no data.Quoted 7 lines
Am I missing something, or it is not marketing what we are talking about?
please I do not understand your point.For what I understand... I was not supposing reiser4 users to be so mutch, but this is very usefull because this means that there are more possibilities to test the code well and to fix bugs... ...
I'm sorry for saying it that directly, and this is not meant against you personally:
Your statement is a good example why this data is worse than having no data.
As I already said in this thread:
<-- snip -->
You are able to say that based on klive data, reiser4 has at least 35 users in the world.
But you can not tell based on klive data whether the ratio of reiser4:ext3 users in the world is more like 1:5, 1:500 or 1:50000.
<-- snip -->
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data. But claiming it based on the klive data is worse since people like you are getting the wrong impression it was based on data that would have the quality for supporting such a statement.
The data simply has not the quality for such a statement. Please read my two examples in [1] if you want to get an impression why such problems can occur.
cu Adrian
[1] http://lkml.org/lkml/2006/7/26/203
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 7 lines · Luigi Genoni
Still I am missing something.
I am not interested in discussing about 1:5 ora 5:1 or so on.
I am not even interested if reiser4 users are 35 or 35000.
But if some people felt they need reiser4 to get their work done, that means something. The numbers and the datum per se are meaningless.
...
You answered to an email where I talked about the wrong assumption the klive data could support the 1:5 market share claim.
This is completely independent from discussions about why users might need reiser4, or which technical or social problems prevent its merging (unless of course someone wants to justify its merging wrongly with the 1:5 claim), and therefore your answer does not apply to this part of the thread.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
I answered a mail about how klive data should not be took in account, and could even be dangerous...
Quoted 34 lines · Adrian Bunk
Quoted 8 lines · Luigi Genoni
Still I am missing something.
I am not interested in discussing about 1:5 ora 5:1 or so on. I am not even interested if reiser4 users are 35 or 35000. But if some people felt they need reiser4 to get their work done, that means something. The numbers and the datum per se are meaningless. ...
You answered to an email where I talked about the wrong assumption the klive data could support the 1:5 market share claim.
This is completely independent from discussions about why users might need reiser4, or which technical or social problems prevent its merging (unless of course someone wants to justify its merging wrongly with the 1:5 claim), and therefore your answer does not apply to this part of the thread.
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 2 lines · Luigi Genoni
I answered a mail about how klive data should not be took in account, and could even be dangerous...
... and you talking about people who might need reiser4 was therefore a wrong answer.
I never said reiser4 shouldn't be merged, but this wasn't the topic of this subthread.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Luigi GenoniLuigi Genoni <[email protected]> wrote:
[...]
Quoted 2 lines
Anyway you have a datum.
Some people need reiser4, period.
Nope. Some people run kernels that include reiser4. That is all you can infer, and that I knew beforehand. They are at least 35, and that I'd have guessed in any case.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 10 lines · Horst H. von Brand
Luigi Genoni <[email protected]> wrote:
[...]
Quoted 2 lines
Anyway you have a datum.
Some people need reiser4, period.Nope. Some people run kernels that include reiser4. That is all you can infer, and that I knew beforehand. They are at least 35, and that I'd have guessed in any case.
35.5 as I'm testing it here on my workstation and it seems to be faster when you test some things involving many copies of large multi-level sourcetree directories each 3 to 6GiB big in size. 2.6.18-rc2-mm1 with Reiser4 looks ok so far and I had no sync() OOPS like the last time with one -mm revision.
speed tells us nothing about reliability of course, but compared to ext3 with dir_index,sparse_super Reiser4 seems to handle "du -sh" and "rm -r" much faster and without eating all of the CPU cycles as it finishes quicker although Reiser4 was meant to be CPU-heavy compared to ext*/reiserfs3.
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Horst H. von BrandQuoted 2 lines · Horst H. von Brand
Nope. Some people run kernels that include reiser4. That is all you can infer, and that I knew beforehand. They are at least 35, and that I'd have
Well, if they were sure they could never get any benefit by reiser4 they wouldn't be testing it in the first place...
But certainly the fact they're testing it, doesn't mean they're actually going to use it forever. You can monitor the 35 users live with this link and to see if they increase or decrease over time ;)
They're ordered by cumulative uptime and not by the number of users. For example there are only 10 jfs users but those 10 jfs users have a much larger average uptime (59 days) so they score much higher in the cumulative uptime too. Why the average reiser4 uptime is much lower is unknown, it could be because they shutdown the system by night, or because they upgrade kernel so frequently, or because the system crashes.
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Horst H. von BrandSince reiser4 is not something enabled by default into a default kernel distribution, I assume they enabled it knowing what they where doing because they wanted to use it.
Quoted 25 lines · Horst H. von Brand
Luigi Genoni <[email protected]> wrote:
[...]
Quoted 3 lines
Anyway you have a datum.
Some people need reiser4, period.Nope. Some people run kernels that include reiser4. That is all you can infer, and that I knew beforehand. They are at least 35, and that I'd have guessed in any case. --
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 5 lines · Luigi Genoni
Since reiser4 is not something enabled by default into a default kernel distribution, I assume they enabled it knowing what they where doing because they wanted to use it.
Or because they did 'allmodconfig' or 'allyesconfig'. Whenever I build a kernel I enabled everything possible as a module in case I ever need it. For instance, a few weeks ago I had the reiserfs module loaded because I was testing something, if I had klive running it would have said that I use reiserfs when in fact I don't.
Jim.
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 5 lines · Jim Crilly
Or because they did 'allmodconfig' or 'allyesconfig'. Whenever I build a kernel I enabled everything possible as a module in case I ever need it. For instance, a few weeks ago I had the reiserfs module loaded because I was testing something, if I had klive running it would have said that I use reiserfs when in fact I don't.
reiserfs would showup in the module list in such case, but _not_ in the fs list. KLive records both the modules loaded _and_ the mounted fs.
This is the code that records the FS:
if CONFIG_FS:
fs = {}
for _fs in [ re.search(r'^[^\s]+\s[^\s]+\s([^\s]+)', x).group(1)
for x in file('/proc/mounts').readlines() ]:
if _fs not in ['rootfs', 'proc', 'devpts']:
fs[_fs] = None
fs = ' '.join(fs.keys())
KERNEL += str_append(fs)/proc/mounts only lists the _mounted_ fs, not the fs loaded into the kernel statically or with insmod.
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Luigi GenoniLuigi Genoni <[email protected]> wrote:
[...]
Quoted 3 lines
Since reiser4 is not something enabled by default into a default kernel distribution, I assume they enabled it knowing what they where doing because they wanted to use it.
You know, I compile ReiserFS, JFS and XFS (and also CRAMFS and ROMFS) into my self-compiled kernels too. Haven't used any of them in ages (if ever), but one more go at compile-testing won't hurt...
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 2 lines · Horst H. von Brand
You know, I compile ReiserFS, JFS and XFS (and also CRAMFS and ROMFS) into my self-compiled kernels too. Haven't used any of them in ages (if ever),
If you never mounted them shortly after boot time, they would have never showed up in KLive fs list if that's what you mean.
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Adrian BunkQuoted 7 lines · Adrian Bunk
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data. But claiming it based on the klive data is worse since people like you are getting the wrong impression it was based on data that would have the quality for supporting such a statement.
Quoted 5 lines
The data simply has not the quality for such a statement. Please read my two examples in [1] if you want to get an impression why such problems can occur.
Also, one may wish to invest in the purchase of 'How to Lie with Statistics'[1] by Darrel Huff (ISBN 0-393-31072-8). An easy yet powerful little read.
[1] this is not meant to imply that anyone here is lieing, attempting to lie, thinking of lieing, wishing they were lieing or having anything to do with lieing, purposeful or otherwise.
Signature · 3 lines
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael KirbyRe: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Adrian BunkQuoted 11 lines · Adrian Bunk
But you can not tell based on klive data whether the ratio of reiser4:ext3 users in the world is more like 1:5, 1:500 or 1:50000.
<-- snip -->
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data.
Yes, but I have been surprised that linux conference attendees all know about reiser4, so I think it is consistent with the notion that reiser4 usage may well be much much higher than one would expect of a filesystem that is not in the main tree, and which requires a lot of hassle to install. It is a datapoint. I think the level of hobbyist enthusiasm seen suggests that distros may gain market advantage by adding reiser4 support.....
Hans
Re: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
Quoted 13 lines · Hans Reiser
Quoted 11 lines · Adrian Bunk
But you can not tell based on klive data whether the ratio of reiser4:ext3 users in the world is more like 1:5, 1:500 or 1:50000.
<-- snip -->
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data.
Quoted 5 lines
Yes, but I have been surprised that linux conference attendees all know about reiser4, so I think it is consistent with the notion that reiser4 usage may well be much much higher than one would expect of a filesystem that is not in the main tree,
...
There were already several long flamewars^Wdiscussions about reiser4 on linux-kernel.
There has already been some amount of press articles covering reiser4.
But how much usage is the result of this?
There seem to be the the following possibilities how users get reiser4 into their kernel today:
1. -mm kernel
2. non -mm kernel
a) patch downloaded from namesys.com
b) through their distribution
- in a kernel image
- as patch
c) patch forwarded through other channels
2b) seems to be the only number that is easily measurable. Do you have some download statistics for namesys.com?
Multiplying the downloads for the 2.6.16 patches with 10 seems to be the best estimate for the order of magnitude of current reiser4 users that seems to be available.
Quoted 1 line
Hans
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: the ' 'official' point of view' expressed by kernelnewbies.org regarding reiser4 inclusion
In reply to Hans ReiserQuoted 11 lines · Hans Reiser
Quoted 8 lines · Adrian Bunk
But you can not tell based on klive data whether the ratio of reiser4:ext3 users in the world is more like 1:5, 1:500 or 1:50000.
<-- snip -->
I can't prove that the 1:5 ratio is wrong, but the point is that claiming a 1:5 ratio was true based on the klive data is not better than claiming it based on no data.
Quoted 7 lines
Yes, but I have been surprised that linux conference attendees all know about reiser4, so I think it is consistent with the notion that reiser4 usage may well be much much higher than one would expect of a filesystem that is not in the main tree, and which requires a lot of hassle to install. It is a datapoint. I think the level of hobbyist enthusiasm seen suggests that distros may gain market advantage by adding reiser4 support.....
Great! Then /sit down and do the work to get it into the vanilla kernel/. You know then it is not a wasted effort... and you /do/ know by now (or should) that playing the "politics"/"whining" card goes nowhere.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 10 lines · Adrian Bunk
Quoted 9 lines · On Wed, Jul 26, 2006 at 11:17:41PM +0200, [email protected] wrote:
Quoted 5 lines · Adrian Bunk
But depending on the nature of the error, the worst case might be the common case (as I've already explained in another email).
If you can't ensure the quality of your data, please don't use this data to wrongly draw any conclusions from them [1].
Please read the footer of the KLive pages:
Quoted 8 lines
Quoted 3 lines
"The use of the information and of the software in this website is at
your own risk. KLive probably doesn't represent a reliable sample of the real usage of the Linux Kernel."It was you who wrongly said:
"With KLive I can attempt to estimate market share of _kernel_ code"Hadn't you read your own disclaimer?
There is no contradiction in the two statements. To attempt to estimate something I don't need a reliable sample of the whole population. Estimation is still a statistical thing. Also I said attempt to estimate, it doesn't mean I will make it.
If you don't consider those results a positive for reiser4, it can only mean you expected reiser4 to have a much higher share among the KLive users. This is obvious.
Quoted 2 lines
Every time someone will repeat the "1:5 ratio for reiser4:ext3 users", this will be an additional proof it's really worse than no data.
If they say "1:5 ratio for reiser4:ext3 KLive users" everything will be correct and nobody can object because it's a fact.
I said myself that I'm no reiserfs user, and I don't plan to become one any time soon (especially on my production systems), I'm only reporting plain numbers as KLive measured the stuff. I'm surprised as much as you are, but then I've to report facts, and not my own opinions.
As far as I'm concerned the thing I like less of reiser4 is the plugin thing, I'd be less concerned if that was a microkernel (fuse-like) userland plugin system. Anyway with time perhaps things can change and become userland based, and the stuff can be moved into vfs if that code really belongs there as some kernel developer says. That doesn't mean reiser4 can't be merged first and the stuff moved into vfs later. xfs when was merged also pratically rewrote a vfs internally that was meant to work with irix, if Christoph didn't complain about xfs being merged, I don't see what's the problem of reiser4 being merged even if it rewrites some part of vfs. xfs is also still having various special features like the pinhole one that only belongs to the vfs instead but nobody complains.
And if reiser4 is really so bad as they say, once people starts losing data they will spread the word of not using it. As long as it's marked experimental I don't see a big issue, the wireless driver for broadcom chip will eat your filesystem too if the reverse engineered dma operations writes into a buffer header instead of an skb.
Quoted 10 lines · On Thu, Jul 27, 2006 at 01:52:29PM +0200, [email protected] wrote:
On Thu, Jul 27, 2006 at 08:56:03AM +0200, Adrian Bunk wrote:
...Quoted 4 lines
It was you who wrongly said:
"With KLive I can attempt to estimate market share of _kernel_ code"Hadn't you read your own disclaimer?
There is no contradiction in the two statements. To attempt to estimate something I don't need a reliable sample of the whole population. Estimation is still a statistical thing. Also I said
Sure, you don't need any data to estimate anything.
But if your estimate is based on bad data it sounds better than if it was based on no data although the value of the estimate is the same.
Quoted 1 line
attempt to estimate, it doesn't mean I will make it.
Giving low quality raw data and then saying "it wasn't me who did the estimate" is silly.
Quoted 3 lines
If you don't consider those results a positive for reiser4, it can only mean you expected reiser4 to have a much higher share among the KLive users. This is obvious.
That's completely wrong.
I consider those results neither positive nor negative for reiser4.
They could only be considered positive if someone expected less than 35 reiser4 users worldwide.
Quoted 5 lines
Quoted 2 lines
Every time someone will repeat the "1:5 ratio for reiser4:ext3 users", this will be an additional proof it's really worse than no data.
If they say "1:5 ratio for reiser4:ext3 KLive users" everything will be correct and nobody can object because it's a fact.
And 90% of all people will misread it.
And many people will spread it wrong.
That's exactly where such data is worse than no data.
You could claim you know your the suboptimal quality of the data and that you had a disclaimer.
But did you read Hans' reaction on your email?
If you are intelligent (which I assume), you should have learned by this how to not present your data.
Quoted 6 lines
I said myself that I'm no reiserfs user, and I don't plan to become one any time soon (especially on my production systems), I'm only reporting plain numbers as KLive measured the stuff. I'm surprised as much as you are, but then I've to report facts, and not my own opinions.
...
I have no plans to use reiser4 myself (I'm a happy ext2 user). But I'm not against mergng reiser4, either.
I'll leave this technical discussion to the people who know more about this.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 2 lines · Adrian Bunk
They could only be considered positive if someone expected less than 35 reiser4 users worldwide.
The only thing we know for sure is that 35 out of 500 KLive user are running reiser4, worldwide we have no clue.
Quoted 2 lines
If you are intelligent (which I assume), you should have learned by this how to not present your data.
I think readers are intelligent enough too to interpret the KLive data properly for themself, without you having to prevent their eyes to see the raw KLive data.
When you tell me how I should not present my data, you're asking me to censor part or all of the very output of the KLive project. I'd rather wipe out KLive completely, than to censor it. The way I presented it was absolutely not biased, if you can make more transparent and unbiased sql queries than the ones I did, please post them and I'll be glad to run them.
Quoted 1 line
[..] (I'm a happy ext2 user).
Oh my, I hope you're only choosing the fs for your own workstation.
Even though I don't pretend to fully understand someone who claims to be happy with ext2, I've no idea why you hate so much the stuff running at cpushare.com domain. But if it helps KLive is actually one of the non commercial projects I'm hosting there, and the only reason I keep it there, is to be sure not to find it filled by ads.
Now let's try to get some work done instead of only sending emails ;)
Quoted 14 lines · On Thu, Jul 27, 2006 at 03:10:32PM +0200, [email protected] wrote:
Quoted 2 lines · Adrian Bunk
They could only be considered positive if someone expected less than 35 reiser4 users worldwide.
The only thing we know for sure is that 35 out of 500 KLive user are running reiser4, worldwide we have no clue.
Quoted 2 lines
If you are intelligent (which I assume), you should have learned by this how to not present your data.
I think readers are intelligent enough too to interpret the KLive data properly for themself, without you having to prevent their eyes to see the raw KLive data.
Quoted 6 lines
When you tell me how I should not present my data, you're asking me to censor part or all of the very output of the KLive project. I'd rather wipe out KLive completely, than to censor it. The way I presented it was absolutely not biased, if you can make more transparent and unbiased sql queries than the ones I did, please post them and I'll be glad to run them.
What about the following statement:
"Gentoo is 47 times as popular as SuSE among KLive users (a service
offered by a SuSE employee gathering data from many users worldwide)."
Is any part of this information wrong?
Is it therefore OK to put this information to /. ?
Surely not, but you might get the point.
Quoted 6 lines
Quoted 1 line
[..] (I'm a happy ext2 user).
Oh my, I hope you're only choosing the fs for your own workstation.
Even though I don't pretend to fully understand someone who claims to be happy with ext2,
It's stable, and if the machine crashes the fsck is really great (Linus' tree contains at least a dozen patches that had their temporary home in my lost+found). (I don't care that the fsck takes 20 minutes on a 250 GB partition.)
Other people have other preferences and do therefore prefer other filesystems.
Quoted 4 lines
I've no idea why you hate so much the stuff
running at cpushare.com domain. But if it helps KLive is actually one of the non commercial projects I'm hosting there, and the only reason I keep it there, is to be sure not to find it filled by ads.
This isn't against cpushare.com, it's against publishing things people will easily misinterpret.
The Linux Counter [1] is another non commercial project gathering similar data (including live data about running kernels and uptimes) from far more users, and I've already given an example in this thread how someone could have misinterpreted the data offered there. And if someone would argue with data from there in a similar easy to misinterpret way on this list, I'd react similarly.
And another example would be that you could say "one third of all Linux Counter machines are still running kernels < 2.6". This would be based on current information submitted automatically from nearly 5000 machines. But people would read this is "one third of all machines are still running kernels < 2.6". But the data doesn't have the quality for this generalization. And this is exactly the problem.
Quoted 1 line
Now let's try to get some work done instead of only sending emails ;)
Agreed. ;-)
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 10 lines · Adrian Bunk
What about the following statement:
"Gentoo is 47 times as popular as SuSE among KLive users (a service
offered by a SuSE employee gathering data from many users worldwide)."Is any part of this information wrong?
Is it therefore OK to put this information to /. ?
Surely not, but you might get the point.
I already told you once that such a claim is totally bogus because KLive _doesn't_ record anything about the _userland_, it only records kernel stuff.
It's not Dlive (distributon Live), it's KLive and K stands for _kernel_ not distributions.
Not sure how many times I'll have to remind you about this.
Also note currently the current cumulative uptime ratio is 1:18 not 1:47 and even the ratio of the number of users is 1:42. The only claim based on actual facts you can try to publish on the press is this:
"The Gentoo kernels are 18 times more popular than the SUSE kernels among KLive users (a service offered in his spare time by a SUSE contractor that tries to gather data from many users worldwide)."
You can also add:
"Another data point is that among the KLive users the Fedora kernels are 24 times less popular then Gentoo ones."
Free to advertise the above if you find it interesting.
Quoted 2 lines
This isn't against cpushare.com, it's against publishing things people will easily misinterpret.
I think people deserve to think for themself without you acting as censorship filter for them.
Quoted 19 lines · On Thu, Jul 27, 2006 at 04:45:29PM +0200, [email protected] wrote:
Quoted 10 lines · Adrian Bunk
What about the following statement:
"Gentoo is 47 times as popular as SuSE among KLive users (a service
offered by a SuSE employee gathering data from many users worldwide)."Is any part of this information wrong?
Is it therefore OK to put this information to /. ?
Surely not, but you might get the point.
I already told you once that such a claim is totally bogus because KLive _doesn't_ record anything about the _userland_, it only records kernel stuff.
It's not Dlive (distributon Live), it's KLive and K stands for _kernel_ not distributions.
Quoted 6 lines
Not sure how many times I'll have to remind you about this.
Also note currently the current cumulative uptime ratio is 1:18 not 1:47 and even the ratio of the number of users is 1:42. The only claim based on actual facts you can try to publish on the press is this:
The 1:47 was what I calculated yesterday, but it seems to be 1:42 now.
But I'd measure popularity in current usage, not in cumulative uptime.
Quoted 4 lines
"The Gentoo kernels are 18 times more popular than the SUSE kernels among KLive users (a service offered in his spare time by a SUSE contractor that tries to gather data from many users worldwide)."
...
Slightly modified version is now in my .signature (I omitted the "spare time" part since the information is still true and sounds better without it - it would be cencorship if you'd try to force me to not omit it).
cu
Adrian
Signature · 3 lines
The Gentoo kernels are 42 times more popular than the SUSE kernels among KLive users (a service by SuSE contractor Andrea Arcangeli that gathers data about kernels from many users worldwide).
Quoted 4 lines · Adrian Bunk
Slightly modified version is now in my .signature (I omitted the "spare time" part since the information is still true and sounds better without it - it would be cencorship if you'd try to force me to not omit it).
Well, a signature like that, perfectly match the IQ of who writes it, please add a link to the klive homepage too if you don't mind.
This IMHO would be even more hilarious:
"I'm happy with ext2" by Adrain Bunk, the guy who pretends to provide useful feedback in the reiser4 discussion.
Adrian and Andrea, you both write a lot of useful patches, so let's remember that, and try to all get along.....
Hans
Quoted 1 line
remember that, and try to all get along.....
FWIW the last thing I can be interested about is to get along with somebody that gratuitously attacks me every time he can.
Quoted 6 lines · [email protected] wrote:
As far as I'm concerned the thing I like less of reiser4 is the plugin thing, I'd be less concerned if that was a microkernel (fuse-like) userland plugin system.
Performance. If your plugin is performance valuing, it needs to be in
kernel. Also, FUSE does not have per-file plugins (correct me if I err
here). It would be nice to see it pay attention to reiser4 pluginids, and thus become per-file.
Thanks for your other words, which I will not comment on because I agree with them.;-)
Quoted 6 lines · Adrian Bunk
[1] the conclusion itself might or might not be true
e.g. there _could_ be an 1:5 ratio between reiser4 and ext3 users but your data is not in any way able to support or reject this statement
It does however suggest that my surprise at how people at the last Linux Conference I went to all seemed to know that there exists a Reiser4 may be due to it being more widely used than I would have guessed. Maybe there is some coolness factor to having the faster FS that you can't get from any Distro that is enough to overcome the hassle of compiling reiser4progs and a kernel before inserting the DVD. I would not have guessed we had 1/5th of ext3's usage even among lkml readers..... I guess the market contains more people who like technology than I was guessing. Maybe there is a positive word of mouth effect going on too.
It would be nice if SuSE and others at least made it an unsupported option at install time. I shall have to find the time to go asking them all.....
Hans
Quoted 9 lines · Hans Reiser
Quoted 4 lines · Adrian Bunk
[1] the conclusion itself might or might not be true
e.g. there _could_ be an 1:5 ratio between reiser4 and ext3 users but your data is not in any way able to support or reject this statementIt does however suggest that my surprise at how people at the last Linux Conference I went to all seemed to know that there exists a Reiser4
I'd be rather surprised to find someone at a Linux conference who hasn't at least heard of the recurrent flamewars on the topic here...
Quoted 4 lines
may be due to it being more widely used than I would have
guessed. Maybe there is some coolness factor to having the faster FS that you can't get from any Distro that is enough to overcome the hassle of compiling reiser4progs and a kernel before inserting the DVD.
Not seen any data backing up the "faster", let alone so much faster that the hassle (and the risk) would make it worth trying... No, Gentoo folks don't count, around here they are fond of claiming that their self-compiled systems are at least twice as fast as a binary distribution with the exact same software.
Quoted 3 lines
I
would not have guessed we had 1/5th of ext3's usage even among lkml readers.....
I'd guess something of the order of 1/100, for testing purposes and idle curiosity.
Quoted 3 lines
I guess the market contains more people who like
technology than I was guessing. Maybe there is a positive word of mouth effect going on too.
LKML (and Linux conferences) are exactly the places where you /only/ find this kind of people...
Quoted 3 lines
It would be nice if SuSE and others at least made it an unsupported option at install time. I shall have to find the time to go asking them all.....
At least Fedora is trying hard to just follow upstream packages (in this case, Linus' kernels) with the absolute minimum of local patches. It makes good sense, as it reduces the up-front work, and (more important) minimizes the pain when the later official version is somehow incompatible with the previews.
If you want ReiserFS 4 to get more exposure, do the legwork to get it into the official kernel. Distributions should be reluctant to pick it up as long as its status as an official Linux filesystem is in question.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 6 lines · Theodore Tso
Quoted 4 lines · Hans Reiser
Consider what happened with XFS as the article writer mentions. I met the original XFS team, led by two very senior developers (Jim Grey, and another fellow whose name I am blanking on, forgive me, I learned much from him in just a few conversations).
Not sure who Jim Grey was, he never worked on XFS, ah well.
Quoted 6 lines
I believe you are referring to Jim Mostek and Steve Lord, and yes, they were very talented developers and engineers. I very much enjoyed talking to them at various filesystem and Linux conferences and workshops.
Quoted 9 lines
Quoted 5 lines
supervision. What happened? They got hassled. Instead of learning from them, welcoming into our community two very senior developers who knew a lot more than any of us about the topics they chose to speak about, they got hassled, they get ignored, they felt rejected, and left the Linux community forever, never to return.
That's hardly what happened. SGI went through layoffs, and they were hit. See: http://slashdot.org/articles/01/05/26/0743254.shtml
Ted, you of all people should know not believe all you read on slashdot ;-) 'Linuxcare helping out with the funding' ha!
Both Jim Mostek and I left under our own steam at different times, Jim in 2000 and myself in 2003. SGI still has great technology to work on and, but the you can only take so many years of bad financial results and watching people get layed off.
I still work on Linux, and follow development as much as I can. I keep trying to get back to OLS, but circumstances keep conspiring against me, maybe next year.
Steve Lord
Quoted 9 lines · Steve Lord
Quoted 6 lines · Theodore Tso
Quoted 4 lines · Hans Reiser
Consider what happened with XFS as the article writer mentions. I met the original XFS team, led by two very senior developers (Jim Grey, and another fellow whose name I am blanking on, forgive me, I learned much from him in just a few conversations).
Not sure who Jim Grey was, he never worked on XFS, ah well.
I believe the (mis-)reference is to a famous data-base person, co-author of "Transaction Processing". He is with Microsoft now
(http://research.microsoft.com/~Gray/JimGrayHomePageSummary.htm).
Quoted 2 lines
Steve Lord
Nikita.
Quoted 5 lines · Nikita Danilov
I believe the (mis-)reference is to a famous data-base person, co-author of "Transaction Processing". He is with Microsoft now
(http://research.microsoft.com/~Gray/JimGrayHomePageSummary.htm).
That's what I thought when I saw the name Jim Gray, but as far as I knew he never worked on XFS and never left the Linux community dejected because Linux kernel coding standards requirements before changes were allowed to be merged, when Hans did his name dropping thing.
(I mean geez, if you want really high standards before new code is accepted, take a look at Open Solaris; they have *such* a heavyweight process, with two mandatory signoffs by core Solaris engineers who both have to do a line-by-line review, and with a promise of on-disk and ABI compatibility *forever* ---- that we do more commits in a week than they do in a year....)
- Ted
Quoted 6 lines · Theodore Tso
(I mean geez, if you want really high standards before new code is accepted, take a look at Open Solaris; they have *such* a heavyweight process, with two mandatory signoffs by core Solaris engineers who both have to do a line-by-line review, and with a promise of on-disk and ABI compatibility *forever* ---- that we do more commits in a week than they do in a year....)
That sounds almost like gcc, only worse.
I think there is something of a problem currently, tough. It is getting too hard to get code in if you're not a maintainer for an existing subsystem (reiser4, suspend2...), and too easy when you're a maintainer (ext4, uswsusp...). Ext patches don't get reviewed much outside of the developpers, and they go in pretty much without discussion in any case, except when Linus blows a fuse. Reiser4 would have be in without discussion if it had been a set of patches through time to reiser3, and would have been called 4 only when Linus yelled. I suspect some balancing would be useful.
OG.
Quoted 3 lines · Olivier Galibert
Ext patches don't get reviewed much
outside of the developpers, and they go in pretty much without discussion in any case, except when Linus blows a fuse.
Um, you're kidding, right? We certainly don't make the assumption that we can violate CodingStyle willy nilly and stuff in yacc grammers into ext3 and assume that no one will push back.
In fact we did a lot of work to make sure the patches were clean and mostly ready to be accepted to mainline even before we made the first proposal to push extents to LKML.
Quoted 4 lines
I think there is something of a problem currently, tough. It is getting too hard to get code in if you're not a maintainer for an existing subsystem (reiser4, suspend2...), and too easy when you're a maintainer (ext4, uswsusp...).
It's not fair to assume that the only reason why non-maintainers have a harder time getting changes is because their changes are getting more intensive review. (Although it is the case that we probably do need to get better at reviewing changes that go in via git trees.) A much more important effect is that non-maintainers aren't familiar with coding and patch submission guidelines. For example, in suspend2, Nigel first tried with patches that were too monolithic, and then his next series was too broken down such that it was too hard to review (and "git bisect" wouldn't work). And of course, there are people who assume that the rules shouldn't apply to their filesystem...
- Ted
Quoted 8 lines · Theodore Tso
Quoted 3 lines · Olivier Galibert
Ext patches don't get reviewed much
outside of the developpers, and they go in pretty much without discussion in any case, except when Linus blows a fuse.Um, you're kidding, right? We certainly don't make the assumption that we can violate CodingStyle willy nilly and stuff in yacc grammers into ext3 and assume that no one will push back.
I'm not kidding. I do recognise that the ext* maintainers do a very good and clean job.
Quoted 3 lines
In fact we did a lot of work to make sure the patches were clean and mostly ready to be accepted to mainline even before we made the first proposal to push extents to LKML.
I'm no talking about extends only. Ext3 now is very, very different than the ext2+journal it was at the start, with backwards-incompatible format changes added all the time[1]. These changes went in no-questions-asked.
Quoted 8 lines
Quoted 4 lines
I think there is something of a problem currently, tough. It is getting too hard to get code in if you're not a maintainer for an existing subsystem (reiser4, suspend2...), and too easy when you're a maintainer (ext4, uswsusp...).
It's not fair to assume that the only reason why non-maintainers have a harder time getting changes is because their changes are getting more intensive review.
"only", no, definitively not. The impact is non-negligible though.
Quoted 2 lines
(Although it is the case that we probably do
need to get better at reviewing changes that go in via git trees.)
Ohh yes, a lot better. Just look at ALSA, most of SNDRV_HWDEP* should never have gotten in in the first place, especially some recent ones like SNDRV_HWDEP_IFACE_SB_RC, and even some (SNDRV_HWDEP_IFACE_USX2Y*) are security holes the size of Cleveland. I need to continue documenting the Alsa kernel interface, but I need a new bucket, the first one is overflowing.
Quoted 5 lines
A much more important effect is that non-maintainers aren't familiar with coding and patch submission guidelines. For example, in suspend2, Nigel first tried with patches that were too monolithic, and then his next series was too broken down such that it was too hard to review (and "git bisect" wouldn't work).
All his submissions since 2004 or so? It's a little easy to limit oneself to the last two ones.
Quoted 2 lines
And of course, there are people who assume that the rules shouldn't apply to their filesystem...
It may be a little hard to remove XFS at that point though... And, while it's not a filesystem, I'd love to be pointed to the technical discussion deciding whether uswsusp is a good idea.
OG.
[1] All optional, I know.
Quoted 4 lines · Olivier Galibert
I'm no talking about extends only. Ext3 now is very, very different than the ext2+journal it was at the start, with backwards-incompatible format changes added all the time[1]. These changes went in no-questions-asked.
The patches indeed were reviewed and changes made in response to the reviews. The philosophical/design question about whether or not optional features which, if enabled, would prevent older kernels to mount the filesystem was not asked, no. But that doesn't mean that the code was not reviewed; it was.
I would also note that we didn't intimate that we knew better than the reviewers, or question their motives, or otherwise insult the reviewers such that they might decide they have better things to do than to review our patches, and that might have had something to do with how the code got in relatively painlessly....
- Ted
Quoted 5 lines · Theodore Tso
I would also note that we didn't intimate that we knew better than the reviewers, or question their motives, or otherwise insult the reviewers such that they might decide they have better things to do than to review our patches, and that might have had something to do with how the code got in relatively painlessly....
Now that has a very high impact :-) Hans is not very good at the diplomacy game.
The fact that the ext maintainers are very, very good helps quite a lot too. But I think it doesn't change the fact that if r4 has been a set of patches through time to r3, good or not, there wouldn't be a discussion.
It's maybe the lack of an official development branch, but it looks like the kernel development has become very risk-averse, and the bar is set much higher to accept anything that looks relatively new. Any reason is good to have it dropped, cosmetic or not.
Just to give you an idea, if the criteria applied to suspend2 or reiser4 had been applied to everything else, we wouldn't have at least XFS[1], ALSA[2], sysfs[3] and DRM[4]. Whether it is good or bad is an interesting question itself. But before, code just had to be reasonably sane, and it was expected to be fixed through time. Some even has been (sysfs got better). Now it has to attain an ever moving level of perfection before it has a chanc to be accepted.
Unless you're a maintainer, that is, for which you can get pretty much anything in that doesn't immediatly break the compile through git trees. Thankfully, most of the maintainers are sane.
Don't you think this is a problem?
OG.
[1] CodingStyle is for the weak
[2] You call that a kernel interface? HWDEP? ioctl to read/write samples instead of read/write?
[3] Lifetime rules and locking are for other people to care about
[4] Oh my, people are still trying to fix that one
Quoted 4 lines · Olivier Galibert
The fact that the ext maintainers are very, very good helps quite a lot too. But I think it doesn't change the fact that if r4 has been a set of patches through time to r3, good or not, there wouldn't be a discussion.
That's a huuuuuge leap of logic.
Metadata plugins found in reiser4 are far better done at the VFS level, than burying "reiser4 can look like ext2, if it wishes" functionality inside the filesystem.
I guarantee such a patch to reiser3 would get rejected.
Quoted 4 lines
It's maybe the lack of an official development branch, but it looks like the kernel development has become very risk-averse, and the bar is set much higher to accept anything that looks relatively new. Any reason is good to have it dropped, cosmetic or not.
New stuff goes in all the time.
The bar is set too high in some cases (read: SCSI subsystem submissions), but reiser4 submission cannot be generalized as you have done here. There are very real issues present, that need to be dealt with.
Quoted 7 lines
Just to give you an idea, if the criteria applied to suspend2 or reiser4 had been applied to everything else, we wouldn't have at least XFS[1], ALSA[2], sysfs[3] and DRM[4]. Whether it is good or bad is an interesting question itself. But before, code just had to be reasonably sane, and it was expected to be fixed through time. Some even has been (sysfs got better). Now it has to attain an ever moving level of perfection before it has a chanc to be accepted.
reiser4 tries to be another VFS. That's a bit more than needing additional minor fixes over time.
Jeff
Hi!
Quoted 8 lines
Quoted 5 lines
A much more important effect is that non-maintainers aren't familiar with coding and patch submission guidelines. For example, in suspend2, Nigel first tried with patches that were too monolithic, and then his next series was too broken down such that it was too hard to review (and "git bisect" wouldn't work).
All his submissions since 2004 or so? It's a little easy to limit oneself to the last two ones.
Nigel did not do any submissions in 2004 or so. Check your fact, that stuff was marked 'RFC' and yes I did comment on it.
He did 1 (one) submission that looked like SubmittingPatches at the first sight, and that was very recent.
Stop spreading lies.
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 8 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 5 lines
A much more important effect is that non-maintainers aren't familiar with coding and patch submission guidelines. For example, in suspend2, Nigel first tried with patches that were too monolithic, and then his next series was too broken down such that it was too hard to review (and "git bisect" wouldn't work).
Quoted 5 lines
Quoted 2 lines
All his submissions since 2004 or so? It's a little easy to limit oneself to the last two ones.
Nigel did not do any submissions in 2004 or so. Check your fact, that stuff was marked 'RFC' and yes I did comment on it.
2004-09-16 submission:
http://lkml.org/lkml/2004/9/16/76
http://lkml.org/lkml/2004/9/16/77
http://lkml.org/lkml/2004/9/16/78
http://lkml.org/lkml/2004/9/16/81
http://lkml.org/lkml/2004/9/16/82
http://lkml.org/lkml/2004/9/16/83
http://lkml.org/lkml/2004/9/16/86
http://lkml.org/lkml/2004/9/16/87
http://lkml.org/lkml/2004/9/16/89
http://lkml.org/lkml/2004/9/16/90
2004-11-24 submission:
http://lkml.org/lkml/2004/11/24/93
http://lkml.org/lkml/2004/11/24/94
http://lkml.org/lkml/2004/11/24/95
http://lkml.org/lkml/2004/11/24/96
http://lkml.org/lkml/2004/11/24/97
http://lkml.org/lkml/2004/11/24/98
http://lkml.org/lkml/2004/11/24/100
http://lkml.org/lkml/2004/11/24/101
[58 mails or so total]
Quoted 4 lines
He did 1 (one) submission that looked like SubmittingPatches at the first sight, and that was very recent.
Stop spreading lies.
I am awaiting your apologies.
OG.
suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Hi!
Quoted 15 lines
Quoted 11 lines
Quoted 8 lines
Quoted 5 lines
A much more important effect is that non-maintainers aren't familiar with coding and patch submission guidelines. For example, in suspend2, Nigel first tried with patches that were too monolithic, and then his next series was too broken down such that it was too hard to review (and "git bisect" wouldn't work).
All his submissions since 2004 or so? It's a little easy to limit oneself to the last two ones.
Nigel did not do any submissions in 2004 or so. Check your fact, that stuff was marked 'RFC' and yes I did comment on it.
2004-09-16 submission:
...
Quoted 1 line
Yes, Nigel submitted part of suspend2 here (I do not think he submitted compression code on that day, for example), but then
http://lkml.org/lkml/2004/9/16/347
came:
#I should mention, I'm planning on producing a BK tree with these patches #(and ones to fix issues raised), so you won't have to include a long #list in -mm eventually! It will be on suspend2.bkbits.net (not there #yet).
That sounds like "don't merge it yet, I'll prepare better version" to me.
Quoted 3 lines
2004-11-24 submission:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Okay, this one is important. It starts with
#Hi everyone.
#
#I know that I still have work to do on suspend2, but thought it was high #time I got around to properly submitting the code for review, so here goes.
That looks like request for review, not request for merge. Plus it was
to: lkml, while it should be to: maintainer (or maybe to: akpm). Well, it also says "Suspend 2 merge" in subject..
Quoted 6 lines
Quoted 4 lines
He did 1 (one) submission that looked like SubmittingPatches at the first sight, and that was very recent.
Stop spreading lies.
I am awaiting your apologies.
Okay, 11/24 looked closer to submission than I recalled. So I guess I have to say "sorry".
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 2 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
OG.
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 10 lines · Olivier Galibert
Quoted 2 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
Because Nigel has too much of code to start with, and refuses to fix his design because it would invalidate all the stabilization work.
Plus Nigel did not do very good job with submitting those patches.
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 7 lines · Pavel Machek
Quoted 6 lines · Olivier Galibert
Quoted 2 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
Quoted 6 lines
Quoted 3 lines
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
Because Nigel has too much of code to start with, and refuses to fix his design because it would invalidate all the stabilization work.
Why should he invalidate his stabilization work, and what's in need of fixing? The suspend in the kernel is great, but suspend2 includes both suspend and working resume code as well.
Quoted 2 lines
Plus Nigel did not do very good job with submitting those patches.
They apply, they work. What's not very good about that? Is this being blocked because of a spelling error, or did he mess up the indenting on "signed off by" or what? I realize you may have something other than the download version, but it's been years now.
I would like to see the working suspend (suspend2) in the kernel, and users wanting to debug the resume stuff currently in the kernel could get it under EXPERIMENTAL or some such.
Signature · 5 lines
Bill Davidsen <[email protected]> Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion.
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 21 lines · Bill Davidsen
Quoted 7 lines · Pavel Machek
Quoted 6 lines · Olivier Galibert
Quoted 2 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
Quoted 6 lines
Quoted 3 lines
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
Because Nigel has too much of code to start with, and refuses to fix his design because it would invalidate all the stabilization work.
Why should he invalidate his stabilization work, and what's in need of fixing? The suspend in the kernel is great, but suspend2 includes both suspend and working resume code as well.
Quoted 2 lines
Plus Nigel did not do very good job with submitting those patches.
Quoted 8 lines
They apply, they work. What's not very good about that? Is this being blocked because of a spelling error, or did he mess up the indenting on "signed off by" or what? I realize you may have something other than the download version, but it's been years now.
I would like to see the working suspend (suspend2) in the kernel, and users wanting to debug the resume stuff currently in the kernel could get it under EXPERIMENTAL or some such.
You probably don't realize how offensive this is.
Actually some people have been working really hard to make the in-kernel code work and you could just respect that.
Now, please note the swsusp resume code works for me 100% of the time and I know of many people who use it without any problems. Also I know of some people for whom suspend2 doesn't work. Please take this into consideration.
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
Greetings,
Rafael
RE: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 3 lines
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
This statement worries me for several reasons.
First, I've seen repeatedly blame for "drivers". People might buy it if there was not a working suspend2. I never saw Nigal blame drivers; instead he makes sure to provide working code. In the end, users want a working suspend, and that's what counts.
Second, if the current swsusp maintainers have genuine interest for the users (not just "it works on my machine"), I would think they'd have taken a serious look at why suspend2 has a higher success rate. But from the above comment, you are not even sure why that is, and could only speculate "this probably means (drivers)". I could hardly be convinced that the current maintainers have been trying to work with Nigal to improve Linux suspend.
At last, "maintainer" is not just a title or a feeling of superiority, it's a responsibility of providing a great system to the users. I'll just quote Linus when he was flaming suspend-to-ram a couple of months ago. Replace it with suspend-to-disk at your own will:
"The fact that worries me is that suspend-to-ram DOES NOT WORK FOR PEOPLE. I have never _ever_ met a laptop or machine of mine that "just worked". I've always had to fix something, and people always end up having to do something ridiculous like unlink all modules etc.
If that isn't what worries you, you're on the wrong page."
http://article.gmane.org/gmane.linux.power-management.general/2105
Hua
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 9 lines · Hua Zhong
Quoted 3 lines
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
This statement worries me for several reasons.
First, I've seen repeatedly blame for "drivers". People might buy it if there was not a working suspend2. I never saw Nigal blame drivers;
I don't _blame_ drivers. I only wanted to say this: "If Nigel knows that some drivers need to be fixed and he has working fixes for these drivers, he should have submitted these fixes for merging instead of just keeping them in suspend2". Period.
If I know of a fix for a driver, I always do my best to make sure the fix will get considered for merging at least. The problem is I'm not a driver expert and I can't provide the fixes myself.
Quoted 8 lines
instead he makes sure to provide working code. In the end, users want a working suspend, and that's what counts.
Second, if the current swsusp maintainers have genuine interest for the users (not just "it works on my machine"), I would think they'd have taken a serious look at why suspend2 has a higher success rate. But from the above comment, you are not even sure why that is, and could only speculate "this probably means (drivers)".
No, I'm not sure. If I were, I would fix the problem. Also I'm not quite sure about the higher success rate of suspend2.
Quoted 2 lines
I could hardly be convinced that the current maintainers have been trying to work with Nigal to improve Linux suspend.
This is an offensive comment.
Quoted 4 lines
At last, "maintainer" is not just a title or a feeling of superiority, it's a responsibility of providing a great system to the users. I'll just quote Linus when he was flaming suspend-to-ram a couple of months ago. Replace it with suspend-to-disk at your own will:
This also is offensive, because the current swsusp _does_ work for many people. Actually I've recently tried a couple of various machines on which it "just works", so I will not replace suspend-to-ram with suspend-to-disk below, sorry.
Moreover, if it doesn't and the problem is reported, we do our best to trace it and fix it, but sometimes we just can't do this without access to the hardware in question.
Quoted 6 lines
"The fact that worries me is that suspend-to-ram DOES NOT WORK FOR PEOPLE. I have never _ever_ met a laptop or machine of mine that "just worked". I've always had to fix something, and people always end up having to do something ridiculous like unlink all modules etc.
If that isn't what worries you, you're on the wrong page."
And that's very true. For example, the suspend-to-ram doesn't fully work on my own box and I'm not sure it ever will. However, that's not a fault of anyone who works on this, just broken BIOS and the lack of documentation. This is worrisome and many people work on improving these things, but the matter is notoriously difficult.
Greetings,
Rafael
RE: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 10 lines
I don't _blame_ drivers. I only wanted to say this: "If Nigel knows that some drivers need to be fixed and he has working fixes for these drivers, he should have submitted these fixes for merging instead of just keeping them in suspend2". Period.
If I know of a fix for a driver, I always do my best to make sure the fix will get considered for merging at least. The problem is I'm not a driver expert and I can't provide the fixes myself.
Suspend2 patch is open source. You can always take a look. Moreover, if someone claims suspend2 isn't ready for merge, or the patches Nigal has submitted aren't up to standards, one would guess he'd have done so already. So I don't understand what the above means. Have you asked Nigal whether he had any driver fixes? If you guys are really working together, isn't it very easy to do?
Quoted 6 lines
And that's very true. For example, the suspend-to-ram doesn't fully work on my own box and I'm not sure it ever will. However, that's not a fault of anyone who works on this, just broken BIOS and the lack of documentation. This is worrisome and many people work on improving these things, but the matter is notoriously difficult.
I'm not exactly an expert, but I don't think suspend-to-ram is more difficult than suspend-to-disk (probably quite the contrary), and there are a lot in common.
I am sorry that you find some of the comments offensive, but there isn't really anything personal. It's merely a reflection of the frustration from linux users wrt suspend OVER THE YEARS. I know you guys are hard working, but in the end it's a top-quality suspend that counts, and people's patience has been wearing out, especially when there has been an out-of-tree implementation available for a long time already. Everyone wants to see the current maintainers take a more humble and proactive attitude when working with Nigal instead of just dismissing his "bad design" and bashing his patch quality. It's so easy to block someone's initiative than making it better.
Hua
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 6 lines · Hua Zhong
Quoted 6 lines
I don't _blame_ drivers. I only wanted to say this: "If Nigel knows that some drivers need to be fixed and he has working fixes for these drivers, he should have submitted these fixes for merging instead of just keeping them in suspend2". Period.
Quoted 6 lines
Quoted 4 lines
If I know of a fix for a driver, I always do my best to make sure the fix will get considered for merging at least. The problem is I'm not a driver expert and I can't provide the fixes myself.
Suspend2 patch is open source. You can always take a look.
swsusp is open source. You can always take a look. And you can always submit a patch.
Quoted 1 line
Moreover, if someone claims suspend2 isn't ready for merge, or the
Moreover, if someone claims swsusp is broken, they should attach bugzilla id.
Quoted 3 lines
I'm not exactly an expert, but I don't think suspend-to-ram is more difficult than suspend-to-disk (probably quite the contrary), and there are a lot in common.
As you said, you do not know what you are talking about.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 8 lines · Pavel Machek
Quoted 5 lines · Hua Zhong
Quoted 5 lines
I don't _blame_ drivers. I only wanted to say this: "If Nigel knows that some drivers need to be fixed and he has working fixes for these drivers, he should have submitted these fixes for merging instead of just keeping them in suspend2". Period.
If I know of a fix for a driver, I always do my best to make sure the fix will get considered for merging at least. The problem is I'm not a driver expert and I can't provide the fixes myself.
Quoted 8 lines
Quoted 3 lines
Suspend2 patch is open source. You can always take a look.
swsusp is open source. You can always take a look. And you can always submit a patch.
But you can't get the patch accepted, that's issue causing all this discussion.
Quoted 9 lines
Quoted 3 lines
Moreover, if someone claims suspend2 isn't ready for merge, or the
Moreover, if someone claims swsusp is broken, they should attach bugzilla id.
Quoted 10 lines
Quoted 5 lines
I'm not exactly an expert, but I don't think suspend-to-ram is more difficult than suspend-to-disk (probably quite the contrary), and there are a lot in common.
As you said, you do not know what you are talking about.
That's why people are frustrated. You blow off anyone who tells you the code doesn't work. Do you really think Linus doesn't know what he's talking about when he reported that it didn't work for him? Hua Zhong being "Not an expert" is not the same as not knowing what he's talking about.
Signature · 3 lines
bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Hi!
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Suspend2 patch is open source. You can always take a look.
swsusp is open source. You can always take a look. And you can always submit a patch.
But you can't get the patch accepted, that's issue causing all this discussion.
If you send me a reasonably-sized patch, that actually fixes something, I'm likely to apply it. If you send me 14K line monster...
Quoted 11 lines
Quoted 6 lines
Quoted 3 lines
I'm not exactly an expert, but I don't think suspend-to-ram is more difficult than suspend-to-disk (probably quite the contrary), and there are a lot in common.
As you said, you do not know what you are talking about.
That's why people are frustrated. You blow off anyone who tells you the code doesn't work. Do you really think Linus doesn't know what he's talking about when he reported that it didn't work for him? Hua Zhong being "Not an expert" is not the same as not knowing what he's talking about.
He claims s-t-ram is easier than s-t-disk. That means that he did not do his homework, and did not check the archives on the subject.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
RE: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Pavel MachekQuoted 9 lines
Quoted 1 line
Suspend2 patch is open source. You can always take a look.
swsusp is open source. You can always take a look. And you can always submit a patch.
Quoted 1 line
Moreover, if someone claims suspend2 isn't ready for merge, or the
Moreover, if someone claims swsusp is broken, they should attach bugzilla id.
Pavel,
You can't blame me for not doing these things, because I am not a maintainer. However, you are, and you defend yourself so hard for that position, so if _you_ don't do these things, people complain.
Quoted 4 lines
As you said, you do not know what you are talking about.
He claims s-t-ram is easier than s-t-disk. That means that he did not do his homework, and did not check the archives on the subject.
Oh yeah? Let's check the archives:
"I seriously claim that STR _should_ be a lot simpler than suspend-to-disk, because it avoids all the memory management problems. The reason that we support suspend-to-disk but not STR is totally perverse - it's simply that it has been easier to debug, because unlike STR, we can do a "real boot" into a working system, and thus we don't have the debugging problems that the "easy" suspend/resume case has."
http://thread.gmane.org/gmane.linux.power-management.general/1884/focus=2105
Maybe it's why he didn't like the STR design you had?
Maybe I am still wrong, maybe Linus is wrong too, but you can't attack me not doing my homework.
Hua
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
On Monday 31 July 2006 20:55, Hua Zhong wrote:
]--snip--[
Quoted 5 lines
Quoted 2 lines
He claims s-t-ram is easier than s-t-disk. That means that he did not do his homework, and did not check the archives on the subject.
Oh yeah? Let's check the archives:
Quoted 8 lines
"I seriously claim that STR _should_ be a lot simpler than suspend-to-disk, because it avoids all the memory management problems. The reason that we support suspend-to-disk but not STR is totally perverse - it's simply that it has been easier to debug, because unlike STR, we can do a "real boot" into a working system, and thus we don't have the debugging problems that the "easy" suspend/resume case has."
http://thread.gmane.org/gmane.linux.power-management.general/1884/focus=2105
The "_should_" is important here, IMHO.
I think the problems that we have with getting STR to work on many machines reflect the situation in which we are with respect to the hardware. From the programming point of view it's easy, because if you know how to handle the hardware, it doesn't take a lot to get it right. Still, you need to _know_, and we're talking of things that are hardly documented and require hours of trial-and-error to figure out. Usually, it can only be done by someone who
(a) has access to the hardware in question, (b) has a lot of time, (c) is _very_ determined to make the suspend and resume work on this particular device, because these things are notoriously difficult to debug, and (d),
ideally, knows how to write Linux device drivers. If you own an "exotic" notebook, there's practically no chance to find someone like that who owns one too.
Moreover, even if there are some hardware-related fixes in the wild, we can't just throw them at Andrew to merge, because some kernel developers may think they are not the right fixes. Each fix, before it gets merged, if ever, has to be reviewed by the appropriate driver maintainers and people who know how the related subsystems work. If the fix gets rejected, we can't help it.
For example, we've recently received a fix for a resume-related problem on some IDE chipsets (AMD and NVidia ones), but it has been vetoed by Alan Cox. The Alan's arguments are reasonable and everyone seems to agree that it should be done differently, but the net result, for now, is the problem remains - officially - unfixed (see
http://www.ussg.iu.edu/hypermail/linux/kernel/0607.3/1607.html).
However, Nigel maintains his patch in separation with the mainline kernel and he can include fixes like that into it just fine. He can include whatever he likes, as long as it works, but we just can't do that. You can say he has more freedom, because he doesn't have to take the other people's opinions into consideration, so he can make suspend2 work on a greater number of systems more easily. Yet, he faces the other people's opinions about the things that are in suspend2 whenever he submits it for merging. In other words, the same things that make suspend2 work on machines on which swsusp doesn't may also render it _very_ difficult to merge (eg. if Nigel had decided to include the patch vetoed by Alan into suspend2, the Alan's NAK would have applied to suspend2 as a whole).
Generally speaking suspend2 is a collection of many different solutions, some of them being more or less questionable, in many different areas which should not be considered all at once. There should be a separate patch for each of them, submitted and discussed on its own. Moreover, some of these solutions may be considered as not the right ones and some patches may get rejected, which may affect the next patches etc. Still, this is the way in which the kernel is developed and we have no other way to follow.
Greetings,
Rafael
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Hua ZhongQuoted 7 lines · Hua Zhong
Quoted 7 lines
Quoted 1 line
Suspend2 patch is open source. You can always take a look.
swsusp is open source. You can always take a look. And you can always submit a patch.
Quoted 1 line
Moreover, if someone claims suspend2 isn't ready for merge, or the
Quoted 8 lines
Quoted 2 lines
Moreover, if someone claims swsusp is broken, they should attach bugzilla id.
Pavel,
You can't blame me for not doing these things, because I am not a maintainer. However, you are, and you defend yourself so hard for that position, so if _you_ don't do these things, people complain.
I have taken a look at suspend2 and decided I did not like it. (see archives). If you think parts of suspend2 are useful (== fix problem on hardware you have), separate them and submit them.
If you want to claim that swsusp is broken, you should attach bugzilla ids. Anything else is unhelpful.
I'm maintainer, but that does not mean that I have every possible notebook on earth.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Hua ZhongQuoted 16 lines · Hua Zhong
Quoted 1 line
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
This statement worries me for several reasons.
First, I've seen repeatedly blame for "drivers". People might buy it if there was not a working suspend2. I never saw Nigal blame drivers; instead he makes sure to provide working code. In the end, users want a working suspend, and that's what counts.
Second, if the current swsusp maintainers have genuine interest for the users (not just "it works on my machine"), I would think they'd have taken a serious look at why suspend2 has a higher success rate. But from the above comment, you are not even sure why that is, and could only speculate "this probably means (drivers)". I could hardly be convinced that the current maintainers have been trying to work with Nigal to improve Linux suspend.
At last, "maintainer" is not just a title or a feeling of superiority, it's a responsibility of providing a great system to the users. I'll just quote Linus when he was flaming suspend-to-ram a couple of months ago. Replace it with suspend-to-disk at your own will:
Quoted 5 lines
"The fact that worries me is that suspend-to-ram DOES NOT WORK FOR PEOPLE. I have never _ever_ met a laptop or machine of mine that "just worked". I've always had to fix something, and people always end up having to do something ridiculous like unlink all modules etc.
If that isn't what worries you, you're on the wrong page."
http://article.gmane.org/gmane.linux.power-management.general/2105
That's the way I feel, I'm glad someone who can't be ignored feels the same way. There is always a reason why the working version can't be put in mainline, there's always a reason why it doesn't work on my machines but I'm assured that it works on {someone}'s machine so I must have a bad {bios|setup|partition table|attitude}.
Signature · 5 lines
Bill Davidsen <[email protected]> Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion.
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Hi!
Quoted 5 lines
That's the way I feel, I'm glad someone who can't be ignored feels the same way. There is always a reason why the working version can't be put in mainline, there's always a reason why it doesn't work on my machines but I'm assured that it works on {someone}'s machine so I must have a bad {bios|setup|partition table|attitude}.
Do you have bugzilla # or are you just flaming? Please test 2.6.18-rc2.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Hua ZhongHi!
Quoted 9 lines
Quoted 3 lines
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
This statement worries me for several reasons.
First, I've seen repeatedly blame for "drivers". People might buy it if there was not a working suspend2. I never saw Nigal blame drivers; instead he makes sure to provide working code. In the end, users want a working suspend, and that's what counts.
You seem to be claiming that swsusp is broken, but I do not remember any bugreport from you. So... either provide bugzilla #, or stop spreading FUD.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Rafael J. WysockiQuoted 36 lines · Rafael J. Wysocki
Quoted 33 lines · Bill Davidsen
Quoted 13 lines · Pavel Machek
Quoted 10 lines · Olivier Galibert
Quoted 4 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
Quoted 9 lines
Quoted 5 lines
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
Because Nigel has too much of code to start with, and refuses to fix his design because it would invalidate all the stabilization work.
Why should he invalidate his stabilization work, and what's in need of fixing? The suspend in the kernel is great, but suspend2 includes both suspend and working resume code as well.
Quoted 3 lines
Plus Nigel did not do very good job with submitting those patches.
They apply, they work. What's not very good about that? Is this being blocked because of a spelling error, or did he mess up the indenting on "signed off by" or what? I realize you may have something other than the download version, but it's been years now.
Quoted 10 lines
Quoted 3 lines
I would like to see the working suspend (suspend2) in the kernel, and users wanting to debug the resume stuff currently in the kernel could get it under EXPERIMENTAL or some such.
You probably don't realize how offensive this is.
Actually some people have been working really hard to make the in-kernel code work and you could just respect that.
By respect I take it you mean "don't call attention to the fact that it doesn't work for many people?"
Quoted 6 lines
Now, please note the swsusp resume code works for me 100% of the time and I know of many people who use it without any problems. Also I know of some people for whom suspend2 doesn't work. Please take this into consideration.
That's exactly the answer I've been getting for saveral years, "it works for me and my friends," and "try x.y.z release."
Quoted 4 lines
Moreover, if the swsusp's resume doesn't work for you and suspend2's resume does, this probably means that suspend2 contains some driver fixes that haven't been submitted for merging.
That's been addressed by other people, but the suspend2 patch has been submitted multiple times, if there is some driver fix it certainly has been submitted, just not accepted.
Signature · 3 lines
bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
Quoted 47 lines · Bill Davidsen
Quoted 45 lines · Rafael J. Wysocki
Quoted 42 lines · Bill Davidsen
Quoted 13 lines · Pavel Machek
Quoted 10 lines · Olivier Galibert
Quoted 4 lines · Pavel Machek
So we have 1 submission for review in 11/2004 and 1 submission for -mm merge in 2006, right?
Wrong. I gave a list of dates at the beginning of the month, do you think I threw dice to get them?
Quoted 9 lines
Quoted 5 lines
And could you explain, as suspend maintainer for the linux kernel, how come code submitted for the first time two years ago and with a much better track record than the in-kernel one is still not in?
Because Nigel has too much of code to start with, and refuses to fix his design because it would invalidate all the stabilization work.
Why should he invalidate his stabilization work, and what's in need of fixing? The suspend in the kernel is great, but suspend2 includes both suspend and working resume code as well.
Quoted 3 lines
Plus Nigel did not do very good job with submitting those patches.
They apply, they work. What's not very good about that? Is this being blocked because of a spelling error, or did he mess up the indenting on "signed off by" or what? I realize you may have something other than the download version, but it's been years now.
I would like to see the working suspend (suspend2) in the kernel, and users wanting to debug the resume stuff currently in the kernel could get it under EXPERIMENTAL or some such.
Quoted 7 lines
Quoted 5 lines
You probably don't realize how offensive this is.
Actually some people have been working really hard to make the in-kernel code work and you could just respect that.
By respect I take it you mean "don't call attention to the fact that it doesn't work for many people?"
Sorry, you won't get anywhere by insulting people. If you want to call attention to a problem, please file a bug report.
Greetings,
Rafael
Re: suspend2 merge history [was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion]
In reply to Bill DavidsenHi!
Quoted 6 lines
Quoted 1 line
Plus Nigel did not do very good job with submitting those patches.
They apply, they work. What's not very good about that? Is this being blocked because of a spelling error, or did he mess up the indenting on "signed off by" or what? I realize you may have something other than the download version, but it's been years now.
Ask Nigel or search the archives. I will not repeat myself again.
Quoted 1 line
I would like to see the working suspend (suspend2) in the kernel,
Great. Help with debugging. Alternatively, help Nigel with fixing design problems and separating patches for merge -- that should keep you busy and stop you from trolling on the lists.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Ar Mer, 2006-07-26 am 13:08 +0000, ysgrifennodd Pavel Machek:
Quoted 4 lines
He did 1 (one) submission that looked like SubmittingPatches at the first sight, and that was very recent.
Stop spreading lies.
Pavel, I think you might want to check your facts and then apologize.
Quoted 2 lines · Theodore Tso
both have to do a line-by-line review, and with a promise of on-disk and ABI compatibility *forever* ---- that we do more commits in a week
"forever"? Man, that's hard-core. Is that *really* the guideline, or is it some "might as well be forever in this industry" rule like "5 years"?
Quoted 1 line · Hans
Jim Grey
Sounds like the name of Jim Gray, the famous database and transaction processing expert of IBM, Tandem, DEC and Microsoft.
Neither SGI nor XFS has had the honor of working with Jim Gray.
The original XFS developers and designers include Geoff Peck, Jeff Glover, Adam Sweeney and Doug Doucette, from what I can see from my notes dating back to 1993/1994 on this.
Signature · 3 lines
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401No, it was not him, sigh, I'll have to ask Jim Mostek who it was if I can find a valid email for Jim. There was another guy who was Jim Mostek's peer. I might have the name wrong.