Unix International

Multi tool use
|
As referências deste artigo necessitam de formatação (desde dezembro de 2013). Por favor, utilize fontes apropriadas contendo referência ao título, autor, data e fonte de publicação do trabalho para que o artigo permaneça verificável no futuro.
|
|
Nota: Se procura pelo sistema de medidas, veja Unidades Internacionais.
Unix International (UI) foi uma associação criada em 1988 para promover padrões abertos, especialmente o sistema operacional Unix. Os seus membros mais conhecidos eram a AT&T e a Sun Microsystems. A UI foi criada para contrabalançar a organização Open Software Foundation (OSF), que por sua vez foi criada em resposta à parceria que a AT&T e Sun formaram na época para o desenvolvimento do UNIX System V versão 4. A UI e a OSF representavam os dois lados das "guerras do Unix", que ocorreram entre o final da década de 1980 e meados da década de 90.
Em maio de 1993, os principais membros da UI e OSF anunciaram a iniciativa Common Open Software Environment (COSE). Em março de 1994 a UI se juntou com a OSF para formar uma "nova OSF", que por sua vez se fundiu com a X/Open em 1996, formando o consórcio The Open Group.
Referências |
- (em inglês) Chapter 11. OSF and UNIX International (Peter H. Salus, The Daemon, the GNU and the Penguin)
- (em inglês) UI / OSF merger announcements
ORdTg7Yhr R2PXLV,SJ6w70lLd4yn
Popular posts from this blog
0
I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
2
I've read in different places that it is done for "performance reasons", but I still wonder what are the particular cases where performance get improved by this 16-byte alignment. Or, in any case, what were the reasons why this was chosen. edit : I'm thinking I wrote the question in a misleading way. I wasn't asking about why the processor does things faster with 16-byte aligned memory, this is explained everywhere in the docs. What I wanted to know instead, is how the enforced 16-byte alignment is better than just letting the programmers align the stack themselves when needed. I'm asking this because from my experience with assembly, the stack enforcement has two problems: it is only useful by less 1% percent of the code that is executed (so in the other 99% is actually overhead); and...
0
I'm working on an Android app where the user has to use a camera view to scan a barcode. I've been using Firebase's ML-Kit barcode scanning utility to achieve the actual barcode recognition bit and it's been fantastic. There's only one issue - if given a photo with multiple barcodes in it, it commonly misses at least one of the barcodes. That's problematic because a lot of the barcodes that my users have to scan are on boxes/containers with multiple barcodes. Here's an example Pixel 2 XL box that may need to be scanned: The IMEI barcode in this picture is never picked up by ML-Kit. However; if I crop out everything else and just send the IMEI barcode through ML-Kit picks it up fine. Is there anything I can do to help ML-Kit pick up on all of the barcodes?
...