User talk:Heiser

Hello, Heiser! Welcome to Wikipedia! Thank you for your contributions to this free encyclopedia. If you decide that you need help, check out Getting Help below, ask me on my talk page, or place {{helpme}} on your talk page and ask your question there. Please remember to sign your name on talk pages by clicking

or using four tildes (~~~~); this will automatically produce your username and the date. Finally, please do your best to always fill in the edit summary field. Below are some useful links to facilitate your involvement. Happy editing! — Mikhailov Kusserow (talk) 07:28, 21 July 2008 (UTC)[reply]

Getting started
A tutorial • Our five pillars • Getting mentored How to: edit a page • upload and use images
Getting help
Frequently asked questions • Tips Where to ask questions or make comments Request administrator attention
Policies and guidelines
Neutral point of view • No original research Verifiability • Reliable sources • Citing sources What Wikipedia is not • Biographies of living persons Manual of Style • Three-revert rule • Sock puppetry Copyrights • Policy for non-free content • Image use policy External links • Spam • Vandalism Deletion policy • Conflict of interest • Notability

The community
Build consensus • Resolve disputes Assume good faith • Civility • Etiquette No personal attacks • No legal threats Community Portal • Village pump Signpost • IRC channels • Mailing lists
Writing articles
Be bold in editing • Develop an article The perfect article • Manual of style Stubs • Categories • Disambiguation Pages needing attention • Peer review
Miscellaneous
User name • User pages • Talk pages Clean up: General - Spam - Vandalism Join a WikiProject • Translation Useful templates • Tools • User scripts

Microkernel

That diagram needs to be edited, turned it right side up so the kernel is down and OS services top of it and other applications top of them. You were saying that there is no difference of normal application (example of Open Office) and the OS service because Embedded OS include the application itself. That does not mean that that graph is not right, it just means that we need two graph to tell the difference. Other for normal microkernel OS and other about the microkernel when it is used on embedded OS. The graph what you placed back, shows nonkind information about the OS and system separation and leads user to false information that OS is the whole system and all applications belongs to OS. That false information is important to avoid, so mayby a edit this graph by organising the arrows for better usage http://wiki.riteme.site/wiki/Image:OS-structure2.svg . One of the problems is that these graphs should be supporting the text and not trying to represent all different OS structures in one. The OS structure is always different when talkin about different OS's like Linux or Windows W2K but article should give basic information how so reader understand the text and can do cross references about the information to understand different cases. The current graph gives half-truth about microkernels what you just placed back, but lies about the other half. Golftheman (talk) 12:12, 21 July 2008 (UTC)[reply]

Please fix the monolith-micro-"hybrid kernel" diagram and do not just undo it to version what is not so specific about operating and system border. So do not try to keep misinformation there, but help us to make it better. Golftheman (talk) 14:33, 19 August 2008 (UTC)[reply]

I attribute your use of somewhat inflammatory terms like "lie", "half-truth" and "false information" to you being a non-native English speaker. However, you should watch your language, people are likely to get insulted by what you are saying.

Regarding the diagram, it is technically correct, and not "half truth". These things are my job, I'm a professor teaching and researching operating systems for many years. In the diagram, everything but the "Application" box is the "OS". But that in itself is a simplification, as the "OS" is more than just the kernel even in systems like Linux or Windows. Linux also has servers running in usermode, called demons, these are part of the OS. You could try to include that in the diagram, but this would most likely lead to more confusion, not less. (And, of course, "hybrid kernels" are a marketing term, not a technical one.) heiser (talk) 04:43, 26 October 2008 (UTC)[reply]

L4: german

Die Verbreitung des L4 ist ja phänomenal!

Ich wäre allerdings erfreut, wenn auch die deutsche L4-Seite gelegentlich ein wenig nachgepflegt würde. Mich interessieren vor allem die Entwicklungslinien zum L3, mit dem TÜV SÜD Life Service bis heute erfolgreich arbeitet.

Ich wünsche Glück und gutes Gelingen bei den weiteren Aktivitäten!

Ad.ac (talk) 13:52, 25 October 2008 (UTC)[reply]

Danke. Hab mir gerade mal die deutsche Seite angesehen, und da ist wirklich etwas Arbeit nötig. Z.B. wird bei Verifikation VFiasco erwähnt, das als Projekt seit längerem tot ist, dagegen steht das L4.verified Projekt kurz vor dem erfolgreichen Abschluss.

Leider habe ich aber nicht die Zeit, mich auch noch um deutsche Seiten zu kümmern. Aber es wird ja niemand daran gehindert, Informationen aus der englischen Seite auf Deutsch zu übersetzen. Zu L3 weiss ich ohnehin nicht besonders viel. In Dresden gibt es zumindest Leute, die mal damit gearbeitet hatten... heiser (talk) 04:54, 26 October 2008 (UTC)[reply]

File:Logo OK-Labs.png

I presume you're talking about File:Logo OK-Labs.png... when you uploaded this you saw the following:

The use of this file is permitted only on Wikipedia.

Dear uploader: This media file, which you just uploaded, has been listed for speedy deletion because you indicated that only Wikipedia has permission to use this file. While it might seem reasonable to assume that such files can be freely used on Wikipedia, since explicit permission to use it was given, this is in fact not the case. [1] [2] Please do not upload any more files with this restriction on them, because content on Wikipedia needs to be compatible with the GNU Free Documentation License, which allows anyone to use it. See our non-free content guidelines for more information.

If you created this media file and want it to be kept on Wikipedia, remove this message and replace this with {{GFDL-self}} to license it under the GFDL, or {{cc-by-sa-2.5}} to license it under the Creative Commons Attribution-ShareAlike license, or use {{PD-self}} to release it into the public domain.

If you did not create this media file but want it to be used on Wikipedia, there are two ways to proceed. First, you may replace this message with one of the fair use tags from this list if you believe one of those fair use rationales applies to this file. Second, you may want to contact the copyright holder and request that they make the media available under a free license.

If you have any questions please ask them at the Media copyright questions page. Thank you.

Even with the "hangon", which was there for about 1/2 hour with no other changes to the image, all images that have the restricted license are deleted as soon as possible. I would suggest that you re-upload the image with the correct templated license {{non-free logo}} (use the previous without the "tl|) and the appropriate Fair Use. Skier Dude (talk) 07:03, 18 April 2009 (UTC)[reply]

which I see you've done in the interim.Skier Dude (talk) 07:04, 18 April 2009 (UTC)[reply]

History of L4 and Mach

Hi. I see you reverted an edit I made to the "History" section of L4 microkernel family. I made that change after someone stuck a {{fact}} tag on the statement that

This induced developers of Mach-based operating systems to move some time-critical components, like file systems or drivers, back inside the kernel.

I looked at our Mach article and a few documents I have discussing Mach, and it seemed that Mach 1.0 and 2.0 had drivers etc inside the "micro"kernel but they were moved out in 3.0. Was I wrong?

Also, do you have any good sources for this stuff? As well as putting them in the article, I'd love to read them ...

While I'm here, let me summarize the history leading to L4 as I understand it:

Mach was (is) a portable microkernel with a fairly heavyweight IPC mechanism
Mach has performance problems
Jochen Liedtke starts a rethink, using a lightweight somewhat-machine-specific IPC mechanism Liedtke SOSP 93
Liedtke shows that Grant, Map and Flush are all you need for operations on address spaces Liedtke SOSP 95
Liedtke and other tweak their design for better performance and other CPUs.

Is this basically right? If not, would you be able to give me any useful links? Thanks in advance — CWC 10:40, 22 August 2010 (UTC)[reply]

Hi,

It is true that Mach moved drivers out of the kernel at some stage, but note that the text (which I may have written a long time ago) talks about "developers of Mach-based OSes", so not necessarily about the official Mach releases. The "facts" tag is justified, but the statement is correct. I'll look for appropriate sources when I get the chance.

In most cases, rather than just kernelising drivers, people moved complete OS servers into the kernel. This is what happened with OSF/1 and NextStep (which lives on as Mac OS X), where a complete BSD kernel was co-located with Mach. To this date, OS X contains Mach, but also BSD in kernel mode, incl drivers (which is I why I have to reboot my box when an upgrade to iTunes is installed).

Your history is essentially right, except L4 has moved on a lot since then...

heiser (talk) 23:50, 22 August 2010 (UTC)[reply]

Thanks, that clears everything up. That info about OS X is interesting ... and sad, I guess. Cheers, CWC 18:06, 23 August 2010 (UTC)[reply]

Response on Microkernel Talk Page

Hi, I left a response on the Microkernel Talk Page which you might like to reply to....--Ozhiker (talk) 23:59, 8 March 2011 (UTC)[reply]

File permission problem with File:Gernot Heiser-2009.png

Thanks for uploading File:Gernot Heiser-2009.png, which you've sourced to Open Kernel Labs. I noticed that while you provided a valid copyright licensing tag, there is no proof that the creator of the file agreed to license it under the given license.

If you created this media entirely yourself but have previously published it elsewhere (especially online), please either

make a note permitting reuse under the CC-BY-SA or another acceptable free license (see this list) at the site of the original publication; or
Send an email from an address associated with the original publication to permissions-enwikimedia.org, stating your ownership of the material and your intention to publish it under a free license. You can find a sample permission letter here. If you take this step, add {{OTRS pending}} to the file description page to prevent premature deletion.

If you did not create it entirely yourself, please ask the person who created the file to take one of the two steps listed above, or if the owner of the file has already given their permission to you via email, please forward that email to permissions-enwikimedia.org.

If you believe the media meets the criteria at Wikipedia:Non-free content, use a tag such as {{non-free fair use in|article name}} or one of the other tags listed at Wikipedia:File copyright tags#Fair use, and add a rationale justifying the file's use on the article or articles where it is included. See Wikipedia:File copyright tags for the full list of copyright tags that you can use.

If you have uploaded other files, consider checking that you have provided evidence that their copyright owners have agreed to license their works under the tags you supplied, too. You can find a list of files you have created in your upload log. Files lacking evidence of permission may be deleted one week after they have been tagged, as described on criteria for speedy deletion. You may wish to read the Wikipedia's image use policy. If you have any questions please ask them at the Media copyright questions page. Thank you. Ronhjones ^(Talk) 22:09, 24 January 2012 (UTC)[reply]

Disambiguation link notification for January 25

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited NICTA, you added a link pointing to the disambiguation page Environment (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 11:10, 25 January 2013 (UTC)[reply]

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:41, 23 November 2015 (UTC)[reply]

ArbCom Elections 2016: Voting now open!

Hello, Heiser. 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)[reply]

ArbCom 2017 election voter message

Hello, Heiser. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

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 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)[reply]

ArbCom 2018 election voter message

Hello, Heiser. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

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 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]