User talk:Schily/Archive 6

Who do you work for Schily?

You appear to be engaged in a one-man war against a range of internet archiving software, and are engaging in large scale deletion and "undo" behaviour without first discussing your intentions.

What's your agenda? — Preceding unsigned comment added by 120.151.160.158 (talk) 02:39, 5 December 2011 (UTC)

You seem to be a one man show that fights for introducing dis-information. Introducing confusing advertizing blocks for zOS does not help. The information you are looking for is already pointed to in the article. I recommend you to read the article first before you try to modify it. --Schily (talk) 09:53, 5 December 2011 (UTC)

Abuse of editing summaries

Please don't abuse the edit summary as you did with this edit. Dishonest descriptions will generally get a change reverted regardless of the quality of the edit. In extreme cases of abuse it will also get the perpetrator blocked from editing. — Saxifrage ✎ 15:33, 25 September 2006 (UTC)

You're welcome to discuss your desired changes with the community at the talk pages of Cdrtools, Cdrkit, and Jörg Schilling. Trying to force them in by repeated editing, or sneaking them in by using deceptive edit summaries, will fail and earn you a very poor reputation. Please reconsider your tactics. Also, please look up the definition of "defamation" before you overstep the tolerance of this project for legal threats without good reason. — Saxifrage ✎ 01:54, 26 September 2006 (UTC)

You seem unfamiliar with the way Wikipedia works. (As for myself, I've been here quite a while and have earned a good reputation. Use ad hominem attacks at the risk of your own credibility. I'm also not a cracker: I am a pseudonymous editor. Wikipedia respects privacy and doesn't care about identity, only about established reputation.) The way a conflict gets resolved is you make the change, find out that someone disagrees (usually by their reverting it) and then you discuss it with them. If a mutually-satisfactory conclusion cannot be found, the input of the wider community is solicited. If it cannot be resolved then, the even-wider input is solicited. Nothing is done by fiat unless you are Jimbo or the Arbitration Committee.

As such, your demand that I restore the page before discussing is tantamount to you saying that you are unwilling to talk unless you get your way. You're welcome to try that, but I can assure you that such a social tactic will fail and Wikipedia is well-set-up to foil such tactics.

Finally, you are welcome, as I have said, to discuss your desired changes at the relevant pages. You are also welcome to discuss your problems with the version I changed them back to. In otherwords, you must explain your objections, not simply say that you don't like the changes. For instance, you claim that your changes are neutral and that the version before was offensive. Please give concrete details that can be dissected and evaluated clearly and openly.

Threats, bullying, and name-calling will fail. That's just how Wikipedia works and I've seen enough people try to force their way that I hope for your own sake that you will stop trying to use those tactics. (Besides, they are morally bankrupt tactics.) You will find it much more effective to work with me and other editors you encounter that to try to "defeat" us. — Saxifrage ✎ 21:05, 26 September 2006 (UTC)

Your edit here asserted that the link was dead; it is a working page. Please use accurate editing summaries TEDickey (talk) 10:46, 16 July 2011 (UTC)

You entered this dead link two times and spammed the WP article. Please verify your links before you enter them to WP and in case that is is an extemely unreliable source (as with your edit) inform yourself on how to back up to more reliable links (e.g. archive.org). --Schily (talk) 09:49, 21 July 2011 (UTC)

Bourne shell section on criticism

I can tell you feel very strongly that the Bourne shell is superior to the C shell based on improvements that were added over the years. But the criticism section isn't the place to work that agenda. All a criticism section should do is state the arguments that people have made with some citations and leave it to the reader to decide. It's not a place to insert personal opinion about which arguments were right. In any event, the list of complaints, however or whenever valid or invalid, do help explain why descendants of the Bourne kept the language but added features, mostly copied from the C shell.

The better place for discussion of the improvements would be in the features section. Frankly, I think that whole section, as just a list of bullets does a disservice to the Bourne shell. A better article would present the whole history of how the Bourne shell evolved and added features over time. This is where you could help make the article much better. Msnicki (talk) 17:12, 29 September 2010 (UTC)

Proposed deletion of Star (Unix)

The article Star (Unix) has been proposed for deletion because of the following concern:

WP:N, WP:COI

While all contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. The speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. 188.104.122.1 (talk) 10:14, 14 May 2011 (UTC)

Nomination of Star (Unix) for deletion

A discussion is taking place as to whether the article Star (Unix) is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/Star (Unix) until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on good quality evidence, and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion template from the top of the article. 87.174.113.246 (talk) 07:04, 27 May 2011 (UTC)

SCCS

Welcome to Wikipedia. We welcome and appreciate your contributions, but we cannot accept original research. Original research also encompasses novel, unpublished syntheses of previously published material. Please be prepared to cite a reliable source for all of your information. Thank you. TEDickey (talk) 09:44, 24 June 2011 (UTC)

And this is why your edits had to be reverted. --Schily (talk) 11:44, 24 June 2011 (UTC)

Edit war

Hello. You appear to be involved in an edit war on List of revision control software. While the three-revert rule is hard and fast, please be aware that you can be blocked for edit warring without making 3 reverts to an article in 24 hours. You are not entitled to 3 reverts and are expected to cooperatively engage other editors on talk pages rather than reverting their edits. Note that posting your thoughts on the talk page alone is not a license to continue reverting. You must reach consensus. Continued edit warring may cause you to be blocked. Toddst1 (talk) 21:28, 24 June 2011 (UTC)

I made one revert after a the result of a discussion was that the claim on the article was proven to be wrong. Unfortunately, the person who introduced the wrong claim immediately reinserted the false claim. Even though he was able to confirm the test results that verified that claim he introduced is wrong. I was in hope to be able to have verifyable facts in the article. --Schily (talk) 21:45, 24 June 2011 (UTC)

Wikipedia does not verify facts. It just lists sources. Own experiments violate WP:NOR. You didn't get that rule right: Tichys paper is not WP:OR because it's not done by a Wikipedia author, it obviously predates WP by a decade or two and was done within the scientific community, which is the appropriate place to do the research. WP just documents. So: Your experiments indicate that we should look for published sources that undermine your theory of SCCS being not slower than RCS. Congratulations. But until then, the only published results we have, even when they do not agree with your own experiments, are that RCS might be faster. --87.174.41.122 (talk) 08:22, 25 June 2011 (UTC)

The more I read such discussions after edit wars, the more I get the impression that some WP authors bend rules in a way to make sure that they are able to publish claims that have been proven to be wrong. Mr. Dickey as the initiator of the current related edit war e.g. ignored the fact that I have given a pointer to research from Larry MacVoy (the author of BitKeeper SCCS) that confirms that RCS is definitely not faster than SCCS (he calls the claim from Tichy the RCS myth) and you also seem to ignore this pointer to this second independent research from Larry McVoy that disproves the claims from Tichy. Is it really WPs intention to provide an infra structure that supports to publish false claims? --Schily (talk) 10:02, 25 June 2011 (UTC)

Actually, Larry MacVoy acknowledges [1] that RCS is optimized for accessing the trunk tip (this is probably the source that you refer to!), and SCCS is only better when you need fast access to arbitrary revisions. He just states that for the use in BitKeeper, SCCS has better performance, due to the need of fast branch access. --87.174.37.97 (talk) 16:04, 25 June 2011 (UTC)

I could not find any mentioning of the "RCS myth", only "The myth about SCCS getting slower is nonsense". This is substantially different. He essentially just states SCCS is not as bad as it is said to be, somewhat implying that SCCS had a pretty bad reputation at that time. See the other discussion on how your WP:OR benchmark was heavily biased towards SCCS. --87.174.37.97 (talk) 16:04, 25 June 2011 (UTC)

RCS is not only slower when accessing older revisions, it is also not faster than SCCS when accessing the latest revision. This is a fact that is also confirmed by Larry McVoy and that is a repeatable result from my test on Solaris. --Schily (talk) 18:31, 25 June 2011 (UTC)

Source Code Control System

Hello Schily. If you are affiliated with some of the people, places or things you have written about in the article Source Code Control System, you may have a conflict of interest, or close connection to the subject.

All editors are required to comply with Wikipedia's neutral point of view content policy. People who are very close to a subject often have a distorted view of it, which may cause them to inadvertently edit in ways that make the article either too flattering or too disparaging. People with a close connection to a subject are not absolutely prohibited from editing about that subject, but they need to be especially careful about following the reliable sources and writing with as little bias as possible.

If you are very close to a subject, here are some ways you can reduce the risk of problems:

1. Avoid or exercise great caution when editing or creating articles related to you, your organization, or its competitors, as well as projects and products they are involved with.
2. Be cautious about deletion discussions. Everyone is welcome to provide information about independent sources in deletion discussions, but avoid advocating for deletion of articles about your competitors.
3. Avoid linking to the Wikipedia article or website of your organization in other articles (see Wikipedia:Spam).
4. Exercise great caution so that you do not accidentally breach Wikipedia's content policies. — Preceding unsigned comment added by 138.246.2.113 (talk) 11:10, 13 July 2011 (UTC)

Please familiarize yourself with relevant content policies and guidelines, especially those pertaining to neutral point of view, verifiability of information, and autobiographies.

For information on how to contribute to Wikipedia when you have a conflict of interest, please see our frequently asked questions for organizations. Please refrain from pushing that your version is official. It is not, as long as the major UNIX operating systems ship their own versions, which predate yours. Thank you. --138.246.2.113 (talk) 17:26, 12 July 2011 (UTC)

Please do not claim that I wrote thing I did not write. I did never write that my version is more official than other versions. My version however is as official as other versions and my version is the only version that is under current development.

The way Mr. Dickey (and since last night you) act however is definitely not aligned with WP rules. If you introduce claims, you of course need to confirm them. Last night, you removed confirmed statemenets that have been introduced by other users (informing about the fact that I am the current maintainer) and you introduced a false claim about licensing. SCCS is definitely not available under various lisenses but either CDDL ot Closed source. I am sorry to see that you seem to be interested in starting an edit war. --Schily (talk) 08:36, 13 July 2011 (UTC)

re: You re-introduced a false claim on Cdrkit

I merely reverted an egregiously problematic edit. I suggest you get a reliable source to publish your interpretation and reference that, solving all of our problems. --Joy [shallot] (talk) 14:54, 22 September 2011 (UTC)

Comparison of revision control software

Your recent editing history at Comparison of revision control software shows that you are in danger of breaking the three-revert rule, or that you may have already broken it. An editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Breaking the three-revert rule often leads to a block. If you wish to avoid being blocked, instead of reverting, please use the article's talk page to discuss the changes; work towards a version that represents consensus among editors. You can post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection. You may still be blocked for edit warring even if you do not exceed the technical limit of the three-revert rule if your behavior indicates that you intend to continue to revert repeatedly.
Please be more constructive. The reasoning that the table is overly complex is reasonable, and the proposed simplification is good. Don't just revert, try to improve things (and understand that most people don't care much about POSIX for revision control systems anymore, since there is a single one in this table that supports it anyway!) --Chire (talk) 12:49, 8 November 2011 (UTC)

Do you really believe I am your edit slave? If you like to modify an article, do it by your own but follow the rules and do not remove information. Your edits need to be reverted as long as you do no more than removing information. --Schily (talk) 15:37, 8 November 2011 (UTC)

Wikipedia is not a sink of information. It is well acceptable to remove (or here: merge) information if this increases readability of the article. The difference between non-POSIX and POSIX keyword expansion is probably not encyclopedically relevant, and can well be merged into a single column of that complex, overly large table. Unfortunately, you again have a WP:Conflict of interest, and want to promote SCCS via POSIX keywords (that nobody else seems to care about, since only BitKeeper seems to support them). What good is a column when there is a single "yes" in it? This doesn't make sense for the table, but should be listed as a comment (or merged with another column - e.g. into "keyword expansion"). --Chire (talk) 15:56, 8 November 2011 (UTC)

March 2012

Your recent editing history at Year 2038 problem shows that you are currently engaged in an edit war. Being involved in an edit war can result in you being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you don't violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly.

To avoid being blocked, instead of reverting please consider using the article's talk page to work toward making a version that represents consensus among editors. You can post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection. --Guy Macon (talk) 13:32, 19 March 2012 (UTC)

I am sorry to see that you do not follow WP rules, so you (Guy Macon) may be blocked because of the repeated vandalim you introduced. Please do not revert things you do obviously not understand. Note that you have been given information that would allow you to understand the background in case you like to inform yourself. --Schily (talk) 13:38, 19 March 2012 (UTC)

Promotional editing

Please do not add promotional material to Wikipedia. While objective prose about beliefs, products or services is acceptable, Wikipedia is not intended to be a vehicle for soapboxing, advertising or promotion. Thank you. TEDickey (talk) 10:48, 22 March 2012 (UTC)

You seem to be completely insane - sorry. I added an OSS hint that has been removed by an unfriendly person before. --Schily (talk) 12:25, 22 March 2012 (UTC)

Welcome to Wikipedia. Although everyone is welcome to contribute constructively to the encyclopedia, we would like to remind you not to attack other editors, as you did on Talk:Bourne shell. Please comment on the content and not the contributors. Take a look at the welcome page to learn more about contributing to this encyclopedia. You are welcome to rephrase your comment as a civil criticism of the article. Thank you.

Your remarks, " Any person with some minimal basic knowlege in UNIX history or with minimal programmings skills will be able to understand that in contrary to you" and "you are missing the needed skills to be able to discuss a topic but still act as if you were the only person on the planet that knows things right" are unhelpful. Even if you disagree, others are still entitled to their opinions and to be treated respectfully. Msnicki (talk) 15:44, 23 March 2012 (UTC)

Redlinks

In this edit your edit summary was "write the article first" implying that a redlink should not have been placed in the article. If that was the only problem then a more appropriate action would have been to remove the linking, not delete the contribution altogether. In any case WP:REDLINK supports the addition of redlinks to subjects which could or should have articles in the future.

If your problem was that it was uncited then you should have said so in the edit summary, and a more appropriate action would have been a {{cn}} template. I am an experienced electrical engineer with nearly half a century of experience, I have been on Wikipedia for five years with well over 30,000 edits, and have contributed several Featured Articles. I don't write rubbish here. Please show a little more good faith. I will find a source for this and re-add it. I trust you will not delete it again. SpinningSpark 12:53, 16 May 2012 (UTC)

If you did mention a well known variant, I could concur. You did however write about a "multi basis transistor" that does not really exist. BTW: reverting things back without first having a related discussion is seen as unfriendly act. --Schily (talk) 14:24, 16 May 2012 (UTC)

Read the contribution again, it is not "multi basis", but "multiple-base" transistor, comparable with multiple-emitter and multiple-collector. They not only exist, but numerous books describe them and scholarly papers report research on them. I have used them in designs myself. I do not see how I am being unfriendly, you have challenged a contribution, and I have provided a reference, as described in WP:V. On the other hand, you utterly failed "to try to find and cite supporting sources yourself" also as recommended in WP:V. Your edit summary failed to give a removal reason so it is only possible to address it by guessing. The redlink question, which is all you mentioned in your edit summary, is a red herring unrelated to whether the material should exist or not. The criteria for inclusion are verifiability, relevance, and due weight. No formatting issue is ever reason for deletion, but rather,should be fixed. SpinningSpark 15:40, 16 May 2012 (UTC)

I was in hope that you understand, while writing a related article, that the transistor you are talking about cannot really exist. There is no problem to build a transistor with more than Emitter or with more than one Collector and in fact these transistor variants really exist. A multi-basis transistor would be a transistor with one Emitter, one Collector and more than one Basis. I cannot imagine how this should be made. It is thus more likely that people use e.g. two transistors in a specific way that would allow to compensate the noise. This is how the basic idea for the bipolar transistor has been discovered by Herbert Mataré in 1942 while he was working on a Duodiode that should allow to compensate the noise in a mixer for a 3 GHz Radar receiver. And BTW: talking about rules in general: such a discussion belongs to the talk page of the transistor article. --Schily (talk) 16:09, 16 May 2012 (UTC)

I feel the need to write this

Schily, as I'm an ordinary guy who does not have much to do with FOSS development, but more FOSS user and supporter, I would like to say sorry for what Debian did to your project and ask to forgive them please. I use Linux most of the time and it is very bad that users have to use lower quality software, created only BY cloning(forking) and FOR the sake of opposing something. I think such cloning should be illegal. I have read a lot about your conflict and I agree with you on your denial of broken patch completely. However, I don't think going CDDL was good idea - this is only my opinion. CDDL was created to destroy FLOSS, by Sun, and it is not a secret - and this is why when you switched licenses a lot of people revolted. That was reflex-like reaction, probably due to the past similar case of OSS vs ALSA. You are original developer and you are not required to accept any, especially broken, patches, you have my highest respect. You are also correct it is illegal to remove your copyright notes and it is simply unethical. Those are things I, GPL lover, understood simply reading your notes on the website. These were sufficient to understand those guys were are scam and that you had no intention to stop support or deny advancements, as well as you demand respect for your work because you love it. But Debian is not made of those guys, and CDDL is really not good. It simply hurts FLOSS. Please, can you consider dual-licensing you work under both CDDL and GPL? This would allow Debian to include your project once again. It would also be cool if you'd document and keep this issue for historical meaning. I think Mark Shuttleworth was only worried because people have problems with optical media AND he would really like to use original software of yours, but CDDL made him problems (just as it was designed to). That said, I thank you for you hard commitment over these years and for not abandoning Linux (to hell with CDDL vs GPL). It would be cool if you review your position regarding to that, but its just my dream :(. I wish you very best, people like you mean a lot for us,non-ms users. Thank you! 77.180.169.93 (talk) 01:57, 23 May 2012 (UTC)

Your claims about the CDDL are of course nonsense. Just because some people spread FUD against the CDDL does not make the CDDL a bad license. In contrary, the CDDL was designed for best interoperability with other licenses. Also note that the GPL was used to attack the cdrtools project and that the FSF did not help against the attacks from Debian. This is why the cdrtools project switched away from the GPL. The current licensing has been confirmed to be without problems by various lawyers, so why should I go back to a license that was used to attack an OSS project? --Schily (talk) 12:21, 4 July 2012 (UTC)

Shebang: «This is about UNIX - not Linux».

In the shebang page, you modified text with comment: «This is about UNIX - not Linux».

I understand that Linux is a subset of Unix. And both are/intend to be POSIX compliant. But the page was related to shebang and so I do not understand your removal! — Preceding unsigned comment added by 77.199.89.101 (talk) 13:19, 3 July 2012 (UTC)

#! is not part of POSIX, so it is a local UNIX enhancement. Your addition was about a patch request for Linux which is definitely not UNIX related - this patch will not apply to UNIX sources. --Schily (talk) 14:26, 3 July 2012 (UTC)

Edits

Please do not remove maintenance templates from pages on Wikipedia without resolving the problem that the template refers to, or giving a valid reason for the removal in the edit summary. Your removal of this template does not appear constructive, and has been reverted. Thank you. TEDickey (talk) 10:52, 26 July 2012 (UTC)

Please try to be constructive and understand that an ecyclopedia should not contain unsourced claims, such as the previous claim that tried to convince people that there is a legal problem. It seems that you are not constructive as you support people who try to add unsourced claims. I removed a maintenance tag that is nonsense as it cannot be resolved the way the initiator likes to. I could however agree, that we keep the maintenance tag for a while to give people the chance to give a verification for their related claim not to be alleged. If nobody is able to prove that there is a legal problem (which is what I expect as nobody could prove that claim during the past 7 years), we of course need to keep "alleged". --Schily (talk) 10:20, 27 July 2012 (UTC)

Notice of Edit warring noticeboard discussion

Hello. This message is being sent to inform you that there is currently a discussion involving you at Wikipedia:Administrators' noticeboard/Edit warring regarding a possible violation of Wikipedia's policy on edit warring. Thank you.

April 2014

You have been blocked from editing for a period of 48 hours for edit warring at Cdrtools, obvious conflict and POV editing, personal attacks. and threats to continue edit warring. Once the block has expired, you are welcome to make useful contributions. If you think there are good reasons why you should be unblocked, you may appeal this block by adding the following text below this notice: {{unblock|reason=Your reason here ~~~~}}. However, you should read the guide to appealing blocks first.  Bbb23 (talk) 00:18, 8 April 2014 (UTC)

Notice

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. The thread is User:Schily.27s_personal_attacks_and_biased_editing_on_Cdrtools_and_other_UNIX_topics. Thank you. LFaraone 16:23, 12 April 2014 (UTC)

Edits to the Cdrtools article

When you notice some corrections that should be made to Cdrtools like this one, please propose them at the talk page (you can use the {{edit request}} template), and someone will make the change for you if we can verify it. You should not be changing the article's text, not even for small and trivial fixes. Diego (talk) 16:57, 14 April 2014 (UTC)

I only made balanced changed. You on the other side recently made unbalanced changes to the cdrtools article like this one where you removed attempts to correct unbalanced claims that should not stay uncorrected. So you should first ask on the talk page before you make edits. Please revert your unbalanced changes. Schily (talk) 17:16, 14 April 2014 (UTC)

You think you made balanced changes, but you have a conflict of interest that makes you misunderstand what Wikipedia editors consider balanced. Our policy forbids you to make any edit that others consider controversial, that's why you were recently blocked.

I have explained what you need to do to make the article more balanced: give us links to web pages that explain why the content is unbalanced, and we will assess whether each claim needs to be corrected. Diego (talk) 13:49, 15 April 2014 (UTC)

If you believe that people with a conflict of interest should not edit a page, please make sure that no person with a COI is editing the page. Let me repeat: At least during the last 4 weeks, I did not add any own claim to the cdrtools page, I just corrected false or unbalanced claims that have been introduced by people with a COI. Schily (talk) 14:11, 15 April 2014 (UTC)

Talkback

Hello, Schily. You have new messages at Diego Moya's talk page.
Message added 12:10, 23 April 2014 (UTC). You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Diego (talk) 12:10, 23 April 2014 (UTC)

be carefull with unfriendly editors

Hello Schily, Some people are waiting for you to fall in a trap. So I think you should avoid edits of cdrtools that get reverted. Because someone will sooner or later report you and try to have your account blocked... Ekkt0r (talk) 14:08, 12 May 2014 (UTC)

Cdrtools

Schily,

I do understand that you have objection to the closure of the RfC in cdrtools but instead of referring to legitimate avenues of appeal, you are engaged in bludgeoning the process and subverting community consensus in Cdrtools article. Given your connection to the topic, I warn you that another attempt in disruptive actions will result in you being reported to WP:ANI.

If you need help find the correct venue of appeal for closure, I will help you find one.

Best regards,
Codename Lisa (talk) 17:46, 12 June 2014 (UTC)

It seems that you don't even see the that fact that you claimed to see a consensus where no consensus is and that you reported a fictive ratio that does not match the reality is the reason for my amazement. In addition, this "Rfc" is not the most important problem in the article. The most important issue is the fact that the article is full of personal attacks and pointers to external personal attacks, which is against WP rules, see my unanswered question related to personal attacks. Note that a personal attack is a claim made against a person when this claim is not verified - in our case the claim that there is a license problem. I encourage you to be collaborative and to only act in cases where you read the whole conversation, which is needed to understand the problems behind. If you are willing to help in the case, you are of course welcome! Schily (talk) 09:14, 13 June 2014 (UTC)

Like I said, if you do not like what I see, there are legitimate courses of actions to take. (If you don't know them, please ask; I am not seeing you asking yet.)

My concern so far is the outcome of RFC alone; nothing else. Even if my concern was other things, I'd have never justified one disruptive action with another disruptive action. No one answered your question posted in WT:NPA because it was inadvertently or deliberately an instance of trolling; hence WP:DFTT.

Best regards,

Codename Lisa (talk) 10:31, 13 June 2014 (UTC)

P.S. You might want to elucidate a little about this "personal attack" issue with a diff and quote. You've been vague about it. If your concern is valid, I can notify ANI and take action against it quickly. Best regards, Codename Lisa (talk) 10:34, 13 June 2014 (UTC)

Calling my question trolling is completely misunderstanding the problem. I was describing the activities of a person that is very active with harming cdrtools. This is no fun but a very problematic person is supported by the WP rules with his attacks and I am looking for a solution. The persom I am talking about writes text with his WP account and text with IP numbers and the cases where he uses IP numbers look very intentional. I created a log of 47 such IP based edits between December 2010 and now that verifies this behavior. The person also attacks cdrtools on his personal website and he tries (via anonymizing remailers) to blackmail Linux distributors that asked their lawyers and thus distribute the original cdrtools instead of the buggy and unmaintained fork from Debian.

Regarding the licensing section: In May 2004, a social attack against cdrtools was started by some people from Debian. These people later came up with the false claim that there was a legal problem in cdrtools in order to distract from their social attacks. They did never send any legally valid verification for their claims and many lawyers confirmed that there is no legal problem. The cdrtools article however quotes the claims from laymen with the intend to create the impression that there is a modicum of truth in these claims. This cannot be seen as a neutral report on this Debian initiated incidence but rather as an attempt to harm cdrtools.

Another problem in the licensing section is the fact that it attacks cdrtools by describing activitied in an intentionally reversed timeline in order to confuse cause and reaction. It would be easy to verify the real timeline as this is something that cannot be faked in the internet.

Any attempt to make the cdrtools article neutral failed so far. I understand an encyclopedia in a way that it may have to report about attacks but without becoming parts of the attackers. In our case, this would require to clearly mention that there is no verification for a legal problem. Schily (talk) 12:00, 13 June 2014 (UTC)

Please give me your list of 47 IPs, the suspected associated WP account, the link to his personal website, link to the social attack and the diffs. I will send them to an admin to block the user and strike out the diffs.

Best regards,

Codename Lisa (talk) 14:20, 13 June 2014 (UTC)

How should I do this? I would usually do this by mail. Schily (talk) 14:51, 13 June 2014 (UTC)

You can post them here. Or if they are very long, create a subpage in you user page, (e.g. User:Schily/Details) and insert the details there. Best regards, Codename Lisa (talk) 18:27, 13 June 2014 (UTC)

@Codename Lisa: Given the length of the list, I believe it is better to have it separated. Are you OK with the sole list of now 51 IP edits in time order? Do you like it to be sorted with respect to the level of unbalanced text? BTW: You might have noticed that the user in question recently identified himself, so the relation between the WP IP edits and the WP Username was already uncovered by him. In order to better understand his global stratey, it would help to know about his activities on his personal web pages with real name and his other anonymous activities against the cdrtools project on other places (e.g. the bugtracking systems of Linux distributors). Schily (talk) 15:02, 17 June 2014 (UTC)

As you might have seen already, I created that page and filled it with a bunch of diffs related to these edits. I hope this helps to understand what's going on. Schily (talk) 15:55, 17 June 2014 (UTC)

Hi again. Thanks for the list. Since I am already involved in the RFC case of Cdrtools, I will have to send the list to a non-involved admin, crat or checkuser clerk for analysis. (I cannot personally process it.) However, given the high number incidents, your best approach would be what we call it a "celebrity defense". This is a method used by celebrities because they receive too much paparazzi coverage. Here is how it works: Your best defense is neutrality. For example, if someone wrote "He chastised this approach", you change it into "he disagree this approach because ...", provide a reason and add a source. This will disarm the attacker and is in accordance to WP:NPOV. The only avenue of attack left for him or her would be edit warring, which will cause other Wikipedians to rise in your defense.

I will send you the name of the admin who would accept this case.

Best regards,

Codename Lisa (talk) 22:48, 17 June 2014 (UTC)

Thank you for looking at it. Schily (talk) 09:50, 18 June 2014 (UTC)

"Calling my question trolling is completely misunderstanding the problem."

That's probably true, but the burden of asking it in right place, right time and right manner is on you. If you are not a troll, please don't behave like one. Make no mistake, it is very difficult not to behave like a troll. But you will learn once you set about it. Best regards, Codename Lisa (talk) 14:28, 13 June 2014 (UTC)

I discovered that your cases have already been taken by WP:ANI, WP:COIN an WP:ANEW. You should have told me. My analysis of the diffs did not reveal a significant change in the situation since those cases. As such, you must follow up the issue with the admins that participated in those topics. But as I advised earlier, you should take up neutrality of point of view as your defense.

Best regards,

Codename Lisa (talk) 12:48, 18 June 2014 (UTC)

I do not understand. What I like to treat is the problem that results from the fact that a user did not only act with an easy to understand conflict of interest that can be checked by looking at a single action each time. The problem we have results from the fact that this user runs coordinated attacks against the project simultaneously on different media. Each incident taken alone may look tolerable, but if you look at all activities, you understand that someone is trying to run a phalanx of coordinated attacks that in total is non-tolerable. This unfortunately can only be understood if the real identity and other pseudonyms of the same person are known, but this requires to disclose his real identity which is not allowed by WP. You may now understand why I said that the WP rules support people that abuse WP just as one of many media to attack a person or a project. Given the problems with the WP rules, this is why I made the proposal to send all available information in a private mail. Only if you have all this information, you will be able to understand what's going on. Schily (talk) 14:01, 18 June 2014 (UTC)

BTW: his recent personal attacks (using his WP login) seem to verify that his motivation may be jealousy on the fact that I am working on UNIX since 35 years and while doing this created a lot of OpenSource software and developed concepts that are now in use on most systems. Schily (talk) 14:37, 18 June 2014 (UTC)

Cdrtools

The article was a mess. I had to shorten it substantially.

I hope the following sentence summarizes your position with respect to the license (it's mostly left as it was before, I only added the collective, not derivative part IIRC):

• Jörg Schilling denies a license problem in cdrtools. In his interpretation, it consists of independent works and thus do not mix incompatible licenses (i.e. it is a collective work, not a derivative work). According to his interpretation, binary versions may be distributed.[12] He continues to develop his version of cdrtools under the CDDL and GPL (mkisofs) licenses, whereas the cdrkit fork has received next to no updates since.

I also added a website, cdrtools.org, which may violate your trademark (?) and appears to be by some Debian developer or user; but I believe it is useful.

Please, let's keep the article short and to the point. Cdrecord is about writing CDs, not about licensing and fighting - the article thus should focus on CD writing, too. I'm considering to move the first paragraph of the licensing section up, and make it more about SCSI and ATA support. Users of your software do need to know why the devices are addressed. In fact I might do this change next... There has been much too much fighting, and that doesn't do any good, or help you in any way. 94.216.209.108 (talk) 13:03, 16 November 2014 (UTC)

RCS vs WP:BLP

As noted on the talk page, your edit makes an insinuation about the rcs developers, which is against WP:BLP. You should be familiar with this guideline TEDickey (talk) 00:22, 20 November 2014 (UTC)

As you should know, I did of course not make any insinuation, I did just write provable facts. For this reason, your message can be seen as a personal attack. You may like to check your attitude of having discussions with other people. If you believe you found a problem, write a polite question that includes sufficient information and verify your claims for correctness first. Schily (talk) 14:28, 24 November 2014 (UTC)

Your comment as written cannot be misinterpreted. Perhaps you meant something different. I did some further investigation, and expanded the discussion here, although I am not satisfied with the presentation (having more information to add), and probably will split-out a new page for the topic. However, the point is documented there. TEDickey (talk) 09:02, 25 November 2014 (UTC)

So what is correct? You misinterpreted my comment and now claim that it cannot be misinterpreted?

BTW: I cannot see how your private web page is related to RCS in with regard to licensing. All I see is an unverified claim from, where you try to tell us that Tichy assigned the Copyright to the FSF. This is obviously wrong as a German cannot assign Copyright - this is forbidden by law. Schily (talk) 11:31, 25 November 2014 (UTC)

My web page comments on facts which I have observed, which you are demonstrably ignorant of. Rather than make excuses about my wording "assigned", you might take the time to verify (as suggested) the quote from the copyright.list file by communicating with the FSF records on the linked page. TEDickey (talk) 01:07, 26 November 2014 (UTC)

Judging from the copyright statement on RCS, it was created by him at "Purdue University, West Lafayette, IN 47907", where US copyright law should apply. Therefore, he should be able to transfer US copyright to the extend that US copyright permits. --Chire (talk) 09:12, 26 November 2014 (UTC)

Agreed (though I considered that in my response last night, and concluded from Schily's comments in other cases that it would be contentious). The quote does not rely on that. By the way, "private webpage" denotes something with access controls, e.g, ".htaccess", whereas Schily uses the term here in a misleading sense, to attack the messenger. Of course, almost all of Schily's edits rely on what he would call his "private webpages", so the point of doing this is lost TEDickey (talk) 09:20, 26 November 2014 (UTC)

You seem to have strange ideas on what a private web page is. A private webpage is a synonym for a personal web page and the quoted web page is apparently a personal web page. But anyway, this page does not contain a verification that the author Tichy did give the permission to put the code under GPL and you again try to attack the messenger for information that do not like. Schily (talk) 11:13, 26 November 2014 (UTC)

The page indicated for purposes of verification of the quote was this (perhaps you meant that, too, to be a "private web page", or you simply did not read any of the page or preceding discussion) TEDickey (talk) 00:31, 27 November 2014 (UTC)

As mentioned already, the webpage you mention does not contain any information related to RCS and your personal web page does not contain a verification for claims related to RCS. Schily (talk) 13:06, 28 November 2014 (UTC)

I'll repeat myself, since you seem to have trouble following the discussion: on my cm-tools page, I commented on a part of what I investigated:

Given that, I agreed that we could use RCS, but that I would provide wrappers to implement the timestamp improvement. Modifying the RCS programs themselves was out of the question (we kept in mind the company lawyers who would steer clear of anything related to licensing). Revisiting this page in November 2014, I see that the pertinent version could have been RCS 4, released as part of 4.3BSD Tahoe or even RCS 3 in 4.3BSD. In either case, at that point in time Tichy (the original author of RCS) had left Purdue to return to Germany (August 1987). Most of the development after the end of 1983 had been done by others. Oddly enough (though included in 4.3BSD), the actual source license was noncommercial. For commercial use (as done by MKS), registration was required. That changed a year later. This is what it says in the Free Software Foundation's .copyright.list (see this page):

RCS Walter Tichy 1989-03-20
Licenses use of RCS with our choice of terms.

The link in "see this page" points to http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html, which says in part:

To check whether papers have been received, look in /gd/gnuorg/copyright.list. If you can’t look there directly, fsf-records@gnu.org can check for you. Our clerk can also check for papers that are waiting to be entered and inform you when expected papers arrive.

I have a copy of the file, which I used for a different investigation. It's not mine to post on some website. However, you can verify it as anyone else could, via email. TEDickey (talk) 02:11, 29 November 2014 (UTC)

So in other words, you again confirm that the website you refer to does not contain information related to RCS licensing but just general information. Regarding RCS relicensing, in our time is is usual to provide certain information electronically as part of the sources - in special if it is known that a piece of software was offered under a different license before.

As the RCS sources do not contain any hint on the license change even though they mention changes since version 3 (which was definitely closed source), this leaves a bad taste. Schily (talk) 17:22, 2 December 2014 (UTC)

I gave the correct information, explained how to verify it. You are choosing to pretend that I said something different. The given source is more than adequate. TEDickey (talk) 00:51, 3 December 2014 (UTC)

As a reminder, your comments are uncivil (multiple points in the linked topic apply) TEDickey (talk) 08:59, 3 December 2014 (UTC)

My impression is that there are many people on WP that are uncivil to you... did you try to find out why? Schily (talk) 10:22, 3 December 2014 (UTC)

Your impression is based on the talk page comments with assorted vandals. If you want to understand the answer to your question, you should observe their behavior more closely. TEDickey (talk) 01:20, 4 December 2014 (UTC)

I am not a vandal and being treated by you as if I were one does not look civil. Schily (talk) 11:32, 4 December 2014 (UTC)

So you say. Pretending that I said or agreed to something after I pointed out that I had not is one of the things that the guideline on civility points out as a defect. By the way, you have digressed from this thread, and have neither responded to directions for how to verify the given quotation, nor offered any constructive comments toward supporting your statements. TEDickey (talk) 01:46, 5 December 2014 (UTC)

I am sorry to see that you do not seem to understand that it would be your task to present a verification of your claim iff/when there was a permission from Mr. Tichy to put RCS under GPL. It you did not digress from that topic, we could have a constructive discussion. Schily (talk) 10:26, 5 December 2014 (UTC)

I've already verified it for my own part. You continue to pretend that I've not told you how you can verify the quote. TEDickey (talk) 01:07, 6 December 2014 (UTC)

So if you ask others to do research in order to allow verification it is ok, but if others ask you to do the same it is not OK? Schily (talk) 13:45, 9 December 2014 (UTC)

BTW: If you do not reply to the last statement from me, you will again diverge. Schily (talk) 10:39, 10 December 2014 (UTC)

I replied. Your statement and deletion of my comment assures me that you are pretending that I did not. TEDickey (talk) 01:04, 11 December 2014 (UTC)

Correct, for a purposeful discussion it is required to stay on the same topic until all important aspects have been explicated. Schily (talk) 10:27, 11 December 2014 (UTC)

So... when are you intending to start addressing the problems with your edits? None of your comments so far have been constructive, several are misconstructive TEDickey (talk) 01:04, 12 December 2014 (UTC)

I always made constructive comments, but you have not been willing to be constructive but rather tried to diverge with any of your messages. So once you make comments that are on topic, you are of course welcome! 14:18, 12 December 2014 (UTC)

Diverging comment removed. Many of the discussions you have with others are driven by your problematic relation to reliable sources. There are two basic problems that can be seen repetitive:

• You make own edits that miss a reliable source
• You claim that reliable sources given by others are not reliable.

This results is an imbalance between your expectations and your own contributions.

You should avoid this imbalance if you like to be taken for serious.

In our specific case, we have a situation where comparable license changes in other projects usually are documented by a file that is included in the source tree. Such a document is missing in the RCS source tree and such a document is not even available in the network. This is why I like to see a reliable source for the permission to change the license of RCS towards the GPL. Schily (talk) 11:46, 15 December 2014 (UTC)

You keep denying what I am reporting. Do you have any response other than to imply that I'm lying? TEDickey (talk) 01:40, 16 December 2014 (UTC)

You keep to refuse to answer my questions: The RCS license was obviously changed by the GNU project. It is the task of the people who changed the license to verify that this change has been done according to the will of the code owner. I am still missing this verification. Can you prove that the license change has been done in compliance to the will of the code owner - in other words can you present us a letter from Mr. Tichy that he is willing to change the license towards the GPL? There is not even the minimum documentation that we can expect from the new maintainers: Something like "The license was changed to GPL on dd.mm.yyyy with permission from Mr. Tichy". I do not want to get obscure hints on that I can ask obscure people, I like to see what seems to be usual practice on the OSS community. Schily (talk) 11:28, 17 December 2014 (UTC)

By the way, your assertion about comparable license changes bears comment: whether or not it is common practice is arguable (and we don't do unsupported argument here). In particular, this was not done by Sun for their release of sccs sources. It gives less information than, for example, the source which I have provided. To aid the reader, here is the relevant license information, which lacks discussion of the changes from the original AT&T, through at least one intermediate step to its final form:

#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# @(#)README.usr 1.9 06/12/18
#

Enclosed in this directory tree is the source code for "SCCS".

The reader may notice that AT&T is not mentioned, for instance, nor is there any mention of the previous licenses under which the source was available. Before asserting that something is common practice, you should have several examples in mind, in particular those with which you have some established association. TEDickey (talk) 09:11, 16 December 2014 (UTC)

Thank you for verifying that you are not interested in a serious discussion!

You are quoting the license header from a file that was written by Sun Microsystems to document how to compile the Solaris specific variant of the SCCS code. As this text was written by Sun, nobody would expect an AT&T Copyright notice in this file. BTW: As the file is specific to the compile environment from Sun for Solaris, this file is part of the archive devpro-sccs-src-20061219.tar.bz2 but has been removed from newer versions of the SCCS source because SCCS now uses a portable buildsystem and thus no longer needs the Sun specific notes. Other files in the SCCS source of course contain AT&T Copyright notices, see below.

Let me add a note to people who don't know that SVr4 is a collaborative work fom AT&T and Sun Microsystems: Since the mid-1990s, Sun owns a full equal Copyright on the UNIX sourcecode. All code that includes a AT&T Copyright notice, a Sun Copyright notice or both (but does not mention additional owners) can be sub-licensed or opensourced by Sun because of this ownership.

The current SCCS source code contains 112 source files (*.h and *.c)

• 88 of them contain a Copyright AT&T (and others)
• 1 of them contains Copyright AT&T but no Copyright Sun Microsystems
• 87 of them contain Copyright AT&T and Copyright Sun Microsystems
• 3 of them contain Copyright Sun Microsystems but no Copyright AT&T
• 111 of them contain Copyright Jörg Schilling (90 of them in addition contain other Copyright notices)
• 21 of them contain only Copyright Jörg Schilling

You see, SCCS sources are in safe state. I wished, RCS was in a similar state. Schily (talk) 11:28, 17 December 2014 (UTC)

You are evading the point as usual. The two examples are comparable. To put it in your terms, since you refuse to show me the lawyers' correspondence concerning the SCCS code, you are obviously concealing something. That may or may not be absurd (depending on your personal involvement), but it's the same. TEDickey (talk) 01:36, 18 December 2014 (UTC)

You again write non-helpful claims.... SCCS has been relicensed by one of the Copyright holders (Sun Microsystems) - the fact that Sun has become Copyright holder with equal rights to AT&T has been discussed in the public in the 1990s already, RCS has been relicensed by unknown people and the act of relicensing is not even documented in the project files. But as usual, you again diverge from the original topic, so it seems there is no hope to continue an on-topic discussion with you. Schily (talk) 10:13, 18 December 2014 (UTC)

Relicensing the code would require some agreement with AT&T, which has not been documented to the extent which you are demanding of RCS. For both, there is available only summary information which tells what the outcome of discussions/negotiations were: there are no private details disclosed in either case. (If you happen to know of some verifiable reliable source for SCCS, it might be interesting to discuss, but so far you have not responded any of my suggestions for those). As I pointed out, the people involved are easily identifiable, and it is simple to find past comments by you regarding some of them which can only be construed as personal attacks. here for instance is a comment about Tichy (using Bing):

Such ignorance seems not uncommon in the university environment to be and unscientific assertions have sometimes devastating. ... lack of scientific rigor in publications

Your English postings have been in the same tone (so I see no reason to doubt Bing), apparently having a long-term grudge against one or more of the developers. Filling in a perceived void with insinuations and attacks on the various developers violates WP:BLP. TEDickey (talk) 01:14, 19 December 2014 (UTC)

You again verify that you are not interested in a fact based discussion and you repeatedly start personal attacks by missinterpreting fact based statements from me. It is even worse: you did not read my previous text.

I already mentioned the fact that Sun aquired the needed rights in the 1990s and that this has been widely discussed in the usenet at that time. If you have not been reading the usenet in the 1990s, I recommend you to do it now - before sending any further inapropriate reply. Schily (talk) 10:41, 19 December 2014 (UTC)

If you have a reliable source, that would be something to discuss. Apparently you have none (otherwise, you would provide one, just to make a point). TEDickey (talk) 00:31, 20 December 2014 (UTC)

Keep in mind, that most of usenet is hearsay, and not suitable for the type of discussion we are having (referring to your demands to see a letter from Tichy, etc.). You might find it in a press release from Sun, but those generally are vague on this sort of thing - and Oracle has done a thorough job of removing that type of information from its websites TEDickey (talk) 01:24, 20 December 2014 (UTC)

List of commercial software with available source code

Hello, Schily. I'm trying to understand the purpose of List of commercial software with available source code. I tried asking the article's creator at Talk:List of commercial software with available source code#False dichotomy but after his explanations I am only more confused. As far as I can tell, you are the only other editor to have commented on the purpose of this article (in this edit). Could I persuade you to have a look at the article and its talk page and let me know what you understand the scope of the list to be? —Psychonaut (talk) 21:18, 4 January 2015 (UTC)

Please do not add or change content without citing a reliable source. Please review the guidelines at Wikipedia:Citing sources and take this opportunity to add references to the article. Thank you. TEDickey (talk) 13:26, 5 February 2015 (UTC)

Well, you edited the article in question and added a claim without giving reliable source. This is why I reverted your edit. Schily (talk) 11:44, 6 February 2015 (UTC)

Z3

The offending claim cited an entry in the Stanford Encyclopedia of Philosophy whose only reference to the Z3 was

Electromechanical digital computing machines were built before and during the second world war by (among others) Howard Aiken at Harvard University, George Stibitz at Bell Telephone Laboratories, Turing at Princeton University and Bletchley Park, and Konrad Zuse in Berlin. To Zuse belongs the honour of having built the first working general-purpose program-controlled digital computer. This machine, later called the Z3, was functioning in 1941. (A program-controlled computer, as opposed to a stored-program computer, is set up for a new task by re-routing wires, by means of plugs etc.)

which doesn't really directly say anything about how the Z3 was programmed. Indirectly, it says:

• the Z3 was a "program-controlled digital computer";
• a "program controlled computer ... is set up for a new task by re-routing wires";

which, if you put them together, would imply that the Z3 was set up for a new task by re-routing wires.

So the reference could be read as supporting the claim that the Z3 was set up by wiring, so, unfortunately, the text of the citation doesn't verify the inverse of the claim - it indirectly verifies the claim.

Wikipedia:Conflicting sources says you handle this either by demonstrating that one of the sources is unreliable or by including both claims. I didn't see myself as being sufficiently authoritative on this topic to just declare the Stanford Encyclopedia of Philosophy article wrong; the person I think wrote the article has written a lot on the history of computing, although mostly about the history of British computing and about Turing in particular. Turing's Bombe was set up by wiring, so perhaps he was thinking of machines like that or like ENIAC, or perhaps he was just over-simplifying (which I think is a mistake here, as at least two of those electromechanical machines, the Z3 and Aiken's Harvard Mark I, were controlled by programs stored as holes punched on film or tape, although the Mark I's data paths could be changed by re-wiring).

I was hoping he'd reply and fix the Stanford Encyclopedia of Philosophy entry, so that it no longer supported the claim. I wasn't going to be bothered by somebody else just deleting the claim, however. :-) Guy Harris (talk) 17:56, 10 August 2015 (UTC)

If you like a reliable source, I recommend to ask Horst Zuse. He tries to collect the heritage from his father, he did set up a website with information and he did create a replica of the Z3. The Enigma was "programmed" by rerouting (replacing rotors with connections) ans the Turing Bombe was a replica of the Enigma,so it used the same rerouting model as the Enigma. BTW: I removed the false claims as there is sufficient reliable information on the Z3 so that we do not need to have those claims floating around. Schily (talk) 23:09, 10 August 2015 (UTC)

Conflict of interest warning

Hello, Schily. We welcome your contributions to the encyclopedia, but when you have an external relationship with some of the people, places or things you have written about in the article cdrtools, you may have a conflict of interest. People with a conflict of interest may be unduly influenced by their connection to the topic. For information on how to contribute to Wikipedia when you have a conflict of interest, see the conflict of interest guideline and frequently asked questions for organizations. In particular, please:

• avoid editing or creating articles related to you, your organization, its competitors, or projects and products you or they are involved with;
• instead, propose changes on the talk pages of affected articles (see the {{request edit}} template);
• avoid linking to the Wikipedia article or website of your organization in other articles (see WP:SPAM);
• exercise great caution so that you do not violate Wikipedia's content policies.

Please familiarize yourself with relevant policies and guidelines, especially those pertaining to neutral point of view, sourcing, and autobiographies. You have a tendency to misunderstand the spirit and letters of our policies, and you have been warned in the past about your conflict of interest with cdrtools. Please refrain from editing the article directly and limit yourself to adding comments at the talk page, or you could be topic banned sooner rather than later. Diego (talk) 18:09, 27 October 2015 (UTC)

Given That you definitely have a conflict of interest, it is you who is not permitted to edit the cdrtools page Schily (talk) 18:10, 27 October 2015 (UTC)

Outing

Please make yourself familiar with the outing policy, which forbids users from revealing any personally information about other users, including their real names, unless they themselves have already explicitly revealed this information on Wikipedia. Repeated failure to abide by this policy can lead to your account being blocked, so please be more careful in the future. thanks. Beeblebrox (talk) 22:35, 30 October 2015 (UTC)

???? Schily (talk) 11:36, 2 November 2015 (UTC)

It's not complicated. Don't use someone's real name unless they have made it public here, on Wikipedia. My only guess, as you have not used any actual words, is that you do not remember doing so. That's ok, and I won't point it out again because it's been removed anyway and drawing further attention to it would be unproductive, just please be more careful about it in the future. Beeblebrox (talk) 21:29, 2 November 2015 (UTC)

I do not call people under their real name unless they have identified themselves before, but I do not keep track where these people identified their real identity. Could you tell me whom you have in mind and how you got attention? Schily (talk) 10:07, 3 November 2015 (UTC)

How about you just use people's WP usernames? That's why they have them to begin with. Beeblebrox (talk) 18:13, 3 November 2015 (UTC)

Please do not remove maintenance templates from pages on Wikipedia without resolving the problem that the template refers to, or giving a valid reason for the removal in the edit summary. Your removal of this template does not appear constructive, and has been reverted. Thank you. TEDickey (talk) 01:40, 12 November 2015 (UTC)

Please do not add maintenance tags for statements that have been authoritativly verified by a pointer to a US patent. Also note that it is really bad practice not to reply on hints on your talk page -> You have been informed and your revert can be seen as an edit war. Schily (talk) 10:11, 12 November 2015 (UTC)

Schily Bourne shell

I can't find sources to support notability, required for a separate article, but I could see a good argument for adding a mention to the Bourne shell article, especially if we can cite a source for the claim that it's the only currently supported version. Unfortunately, the Mascheck [2] isn't very clear about the status of the variants. Another alternative would be a section that simply lists the variants as Mascheck does and includes yours along with the rest. Msnicki (talk) 02:25, 23 November 2015 (UTC)

I am not interested in a separate article, it is sufficient to mention that there is a maintained version derived from the last official AT&T release.

A "citation" for the only supported version may not be available, but we can look at the Bourne Shell in existing distros:

• HP-UX does not have a Bourne Shell, even HP-UX-10.20 from 1996 did not have it.
• AIX (even the most recent version) comes with a Bourne Shell from Svr3 that does not even give the state of the final SVr3 (the state from 1986 - there is no check whether a parameter to "read" is missing - see Maschek)
• Solaris 11 development releases did move the Bourne Shell from /usr/bin/sh to /usr/has/bin/sh in April 2010. Oracle later moved that to /usr/sunos/bin/sh. There is no development and the development between 1989 and 2010 was minimalistic bug fixing.
• Illumos did not touch the Bourne Shell
• Heirloom seems to be more or less dead since 2007.
• The Schily Bourne Shell however had 2800 file updates in 670 commits since 2006. The amount of source code did more then double since 2006 and the amount of code, left over from OpenSolaris is only 1/3 of the current complete source, even if you ignore the amount of code for the find-bultin from libfind.

and we can check what Bourne Shell derivates are available that have been made portable by replacing the non-portable calls to sbrk() to malloc():

• The original V7 shell is available from Geoff Collyer who wrote the sbrk() replacement code for David Korn in the mid-1980s.
• The Korn Shell of course.
• The Schily Bourne Shell includes the sbrk() replacement code from Geoff Collyer since 2012.

The fact that it comes in two compile variants:

• "osh" only portability changes have been applied
• "bosh" with functional enhancements

make it interesting for people who like to see whether a SVr4 Bourne Shell is able to run a specific shell script and to people who like to compare features with code like "dash".

Note that the Schily Bourne Shell is the only modern Bourne Shell that works on Cygwin and it is aprox. 1/3 faster than the /bin/sh from Cygwin when you run a typical "configure" script.

For the notability, it may be of interest that the Schily Bourne Shell is one of only four shells that use vfork():

• csh since aprox. 1979
• My bsh since 1985
• ksh93 since aprox. 2008
• Schily Bourne Shell since summer 2014

Even on SunOS that implements a copy on write based fork() since late 1987, vfork() is still faster than fork(). On my home system, a fork() for the Bourne Shell typically takes 0.2 ms while a vfork() under the same conditions takes aprox. 0.06 ms. This is a performance win of more than 3x.

Since I finished with adding most "bsh" features this summer, I use it as my main interactive shell. Schily (talk) 11:25, 23 November 2015 (UTC)

Tell you what. Propose the change you'd like on the Talk:Bourne shell page and if I can in good faith agree it meets our guidelines, I'll apply it at once. The worst that can happen is that I could be reverted. Msnicki (talk) 21:34, 23 November 2015 (UTC)

It may be the wrong start as I may be biased. I was in hope that someone else could set up an initial text that probably then could be used as base for discussions. But even a short note would help already to inform people about the existence of the Schily Bourne Shell who do not know Sven Maschek. I know that there are unfriendly people at WP that like to prevent information they don't like, so there really may be reverts. See a recent revert from a user that already added own self promoting claims to WP. In the revert I have in mind, he was using a false claims for the revert message after someone just added a link to the Bourne Shell article in the WP article about me. Schily (talk) 12:09, 24 November 2015 (UTC)

ArbCom elections are now open!

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 16:08, 23 November 2015 (UTC)

Korn shell

I was able to find only what appear to be old "Wipro" versions of (to me) uncertain lineage. I could not find where to download anything current for Windows. But I have a suggestion. Our Korn shell article is simply incompetent. It doesn't even have a screenshot of the actual Korn shell, only the pdksh clone but it doesn't show the banner or version and even the contributor seems unclear what this is. It doesn't even demonstrate the shell (whatever shell this is) doing anything interesting. All you really see is the output of ls. What I think is needed is a Linux desktop screenshot of ksh93 (which I take for granted you must have) alongside bash for comparison. Since you're in contact with David Korn, you might ask him for suggestions of what it should show. Put your Schily shell in a third window if you like as the current supported version of the Bourne shell. Msnicki (talk) 17:14, 24 November 2015 (UTC)

My last mails took some time to get answered and usually David does not answer but Glenn does.

I believe that the most important features of ksh93 are:

• runtime-loadable builtins.
• path search for builtins - this was introduced for OpenSolaris, we plan to make this mandatory for the next POSIX release
• many UNIX core commands are builtins - this is something busybox copied from ksh ;-)
• one of the few shells that tries to use vfork()
• needs aprox. 30% less forks than bash
• currently the fastest known shell

How should I identify the Schily Bourne Shell except by asking it for it's version? Schily (talk) 17:32, 24 November 2015 (UTC)

Asking the version in the screenshot seems like the perfect way. If anything (including the version info) needs additional explanation, you could add it as a comment in the window or to the description you give when you contribute it. Msnicki (talk) 17:41, 24 November 2015 (UTC)

Something like this:

bosh
opt joerg> #
sh (Schily Bourne Shell) version 2015/11/15 a+ (i386-pc-solaris2.11)
opt joerg>
opt joerg> bosh -c 'exit 123456790'; echo $?
22
opt joerg> set -o fullexitcode
opt joerg> bosh -c 'exit 123456790'; echo $?
123456790

could show a recent unique feature: retrieve more than 8 bits from the exit code. Schily (talk) 17:48, 24 November 2015 (UTC)

Up to you, but consider that your reader will likely appreciate broad strokes over details. It's easiest if they can relate what you show them to what they already know. Your readers will probably be familiar with loops, wildcarding, variables and expression grammars and with the notion of performance. If one product differs from the others in one of these ways, that's information they'll be able to relate to. They may not be as familiar with exit codes. There's also nothing wrong with showing that they all do the same thing on some interesting example if that's what you think readers would like to know. Msnicki (talk)

I just realized that if you do a nice job and create an attractive, easy-to-understand desktop screenshot image, you could also put it (or something substantially similar, perhaps differing only in which window is on top) on the Bourne shell and Bash (Unix shell) pages, both of which also have absolutely terrible screenshots. Msnicki (talk) 18:16, 24 November 2015 (UTC)

Any new thoughts on some better screenshots? Msnicki (talk) 17:57, 23 December 2015 (UTC)

During the past weeks, I worked on enhancing the Bourne Shell to bring it closer to a POSIX shell. I would need to spend some time in collecting commands to put into the related shell windows for a vanilla Bourne Shell and a Schily Bourne Shell. Do you have any thoughts about which commands to use? Schily (talk) 18:03, 23 December 2015 (UTC)

Rather than a bunch of commands like ls and grep, all external to the shell, I'd show a simple script of some sort to demonstrate the language. You'll find a bunch of examples provided with Hamilton C shell here. Perhaps you could translate a couple of them into sh/ksh scripts. Msnicki (talk) 04:59, 24 December 2015 (UTC)

Given that the Bourne Shell now supports $(cmd) command substitution, does it make sense to mention this in the screenshot? Schily (talk) 11:35, 3 February 2016 (UTC)

Wikipedia:Articles for deletion/Jörg Schilling (2nd nomination)

FYI. As you're so strict on the quality of sources and so hard against "advertizing", maybe you need to work on your CV article a bit more. Viam Ferream (talk) 11:41, 22 January 2016 (UTC)

You seem to miss interpret how Wikipedia works. This is not my CV but a general WP article and the article exists because other people believe that it is useful for WP. Schily (talk) 11:45, 22 January 2016 (UTC)

I would like to think it works by WP:RS, WP:V, WP:N and WP:BLP, not WP:COI. Viam Ferream (talk) 11:47, 22 January 2016 (UTC)

• Separate question, but is your beef with Gnu (and why you remove refs citing them as "advertizing") because you have some other overspill from how (you think) they're doing software licensing wrong? You do seem to like chasing dead horses between articles on wikipedia, thrashing them mercilessly as you go. Viam Ferream (talk) 11:50, 22 January 2016 (UTC)

Please don't put something into my mouth that I did not say. GNU it not a general problem, the general problem is to add deviating and vendor specific information only or first in case there is a standard. You are definitely trying to add unbalanced information. BTW: there are other very active people like e.g. "Tedickey" who revert a lot more informational edits than yours because it is alleged to be advertizing. A vendor specific documentation is always worse than the official standard spec in special as the GNU spec is of type "embrace and extent" and tries to create a vendor lock in via unneeded nonstandard extensions. Also note that WP is not a revenge play. You cannot delete a general article just because your non-neutral edits have been reverted. Schily (talk) 13:17, 22 January 2016 (UTC)

SIGTSTP

Hi Schily/Jörg,

Thanks for 705285715, reverting incorrect gloss of SIGTSTP ("terminal stop"). I had copied it from Unix signal, where it was incorrectly "stop temporarily", and fixed it in 705385335.

I noticed this due to the default messages for reverts, but if you message me I could've corrected it directly (you can always correct it yourself, of course, if you've the time).

Thanks again!

—Nils von Barth (nbarth) (talk) 05:27, 17 February 2016 (UTC)

Please do not attack other editors. Comment on content, not on contributors. Personal attacks damage the community and deter users. Please stay cool and keep this in mind while editing. Thank you. TEDickey (talk) 23:52, 24 February 2016 (UTC)

Mr. Dickey: Please learn what an attack is and what not. This could help to raise your reputation... Schily (talk) 11:38, 29 February 2016 (UTC)

POSIX

Re [3] "It is a well known fact that ..." isn't the same as WP:RS. A claim in a WP article that something is non-compliant still needs to be sourced, partly for WP:V and mostly because many readers won't "know this well" already and they can benefit from an onward link to a deeper analysis of it. Viam Ferream (talk) 09:18, 25 February 2016 (UTC)

Well, you are quoting unreliable information while I am quoting the POSIX standard committee. After Apple passed the POSIX test suite, it was discovered that the test suite is broken and let Apple slip through. Do you see where the difference is? Your claim cannot be validated by reliable sources. Schily (talk) 11:41, 29 February 2016 (UTC)

I'm not quoting anything. I'm looking for you to quote something, for the education of our readers (and a bit about WP:V, what with that being necessary policy and everything).

I know almost nothing OS X and absolutely nothing about its POSIX compatibility. I have literally no opinion on the claim here, I have no knowledge to base such an opinion on. But if OS X does have an issue with some part of the POSIX tests, then we shouldn't just state that here, we should also source it. That has two benefits: it gives readers the chance to read more detail about the issue (Is this a big issue? Is this going to matter to me?) and it also meets the WP:V requirement that claims made on WP should be backed up. Viam Ferream^Talk 11:52, 29 February 2016 (UTC)

Well OS X has many issues. One is that it was certified with bash-3.x and bash-3.x has many well known POSIX issues, it does e.g. not correctly honor the -e flag and as a result, makefiles may continue to execute even though there was an error.

The problem with waitid() is another reason why is is wrong to claim that OS X follows the POSIX rules. Correct is what I wrote: it passed the certification tests even though there are issues. If you are not happy with my explanations, you may try to find something that you would accept as a WP like quotation. For me it is sufficient to be able to give a scientific verification that there is a problem with OS X and POSIX. Schily (talk) 13:49, 29 February 2016 (UTC)

Per WP:V though, we can't just say something is "well known", we also have to link to a WP:RS that actually states it (and if it's really "well known", then such a thing should be easy to find). Maybe this is well known to you, but it's not well known to me and I suspect neither to many of our readers. So can you suggest a RS source that will expand on these issues? I literally don't know what "the problem with waitid()" is. Maybe I would benefit from reading more depth about it? I'm not doubting that there is such a problem, I'm just trying to find good links that cover it in more depth. Viam Ferream^Talk 14:26, 29 February 2016 (UTC)

Well, I published a test program and you referred to it in your first message. If you like to search POSIX standard bugs, I recommend: http://austingroupbugs.net/ here you may also find information about the waitid() implementation bugs in various UNIX implementations. A related bug report caused FreeBSD to fix their kernel around May 2015. waitid() is a base interface from POSIX since ~ 1995 that cannot be made optional. Schily (talk) 16:02, 29 February 2016 (UTC)

Thanks, I'll follow those up. Viam Ferream^Talk 16:10, 29 February 2016 (UTC)

Setuid: Reverting 714962955

@[4] May I ask for an explaination? Especially on what do you mean by “Not an improvement”? --Wikimpan (talk) 20:15, 16 April 2016 (UTC)

sudo is not part of setuid and thus not something that could influence the security if setuid binaries. Schily (talk) 09:30, 18 April 2016 (UTC)

The paragraph wasn’t saying anything about affecting security of setuid-ed binaries. It was about improving security as a whole. setuid provides the same function as sudo — just it’s older and less secure. sudo simply supersedes setuid in most applications. Of course one can also keep sudo just in “See also” section, but I believe it’s more appropriate to give a pointer in a paragraph that deals with security. --Wikimpan (talk) 04:00, 6 May 2016 (UTC)

sudo is not really related to the set-uid bit - not in a way that would make such a hint an improvement. Schily (talk) 13:06, 9 May 2016 (UTC)

4th flight photo

Please see my comment on the Talk:Wright Flyer page. DonFB (talk) 10:40, 26 July 2016 (UTC)

dash

Hi!
Thank you for contributing to the article about the ash. Are you sure, that the dash does not support multi-byte character encoding? I'm using dash 0.5.9.1 and it actually can handle characters lik ć, č, š, ö, ü, ä, ß etc.
--Liebeskind (talk) 13:16, 16 November 2016 (UTC)

It cannot handle them, it just passes them. You may like to try to set IFS to 'ö' and then check what happens.... you get two spaces instead of one between the separated parts of a string if you use UTF-8. Just because the data flow does not prevent 8-bit clean chars, this does not make a program multi-byte aware. It would need to know where character limits are inside a string. Schily (talk) 14:52, 16 November 2016 (UTC)

BTW: given that aprox. 30% of the CPU time of a shell is consumed by the multi-byte handling routines, dash would become slower than bash is someone added multi-byte support. Schily (talk) 17:11, 16 November 2016 (UTC)

ArbCom Elections 2016: Voting now open!

Hello, Schily. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)

Duplicate POV hatnote

About this revert, the article has {{POV}}, but the first section has had {{POV section}} for the past year. Isn’t that redundant to have both? —67.14.236.50 (talk) 12:28, 14 December 2016 (UTC)

The POV tag was added because the named section in special is not neutral. But the rest should be enhanced as well. So if you like, you may remove the second tag. Schily (talk) 14:25, 14 December 2016 (UTC)

“Second tag” being the one added eight months later? I don’t think I understand. —67.14.236.50 (talk) 23:07, 14 December 2016 (UTC)