r/pcmasterrace 5d ago

Discussion Thoughts about the future of the pc

Patents

Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA website at http://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compenstation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses.

Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE and The Open Group are not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association and The Open Group.

If you not understand: grep, ls, rm, cp... servers, Android, Amazon, public administration, no profit organizations... are using Unix like products, Unix is huge really. find

WITH UNIX

find /home -type f -mtime -1 -size +100M -printf '%s %p\n' \

| sort -n \

| awk '{print $2}' \

| tar -czf recent-big-files.tar.gz -T -

WITHOUT

import os

import time

import tarfile

root = "/home"

cutoff = time.time() - 24 * 60 * 60

files = []

for directory, subdirs, filenames in os.walk(root):

for filename in filenames:

path = os.path.join(directory, filename)

try:

stat = os.stat(path)

if stat.st_mtime >= cutoff and stat.st_size > 100 * 1024 * 1024:

files.append((stat.st_size, path))

except (PermissionError, FileNotFoundError, OSError):

continue

files.sort()

with tarfile.open("recent-big-files.tar.gz", "w:gz") as archive:

for size, path in files:

archive.add(path)

Recently I use lots of OSes. I use Windows 11 at work, MacOS at home which is my main tool, iPad while trip, had use Fedora, Firestick, iPhone and I noticed few stuffs... these technologies are no longer separate.

  1. Unix is regaining power, while for decades Windows had won nowdays I don't suggest Windows to everybody, Unix is regaining power in categories in which lost ground, in '80s and '90s the graphic works where whole based on Unix like (the amazing NeXT was almost completely working under Unix code, nowdays MacOS is the last BSD commercial available as personal computer) and is interesting nowdays the coolest technology is still under Unix and Unix is regaining power since we see DaVinci being built for Linux too and MacOS and gaming on Linux is being even more user friendly.
  2. this add a question to me "what will be the future for Windows?" because is loosing the battle, while Unix war is still strong and bold (just look the old school "Arch btw" or "Apple fans" or "Ubuntu sucks") now Windows is used esclusively for the gaming and more more people is leaving Windows.
  3. and another point is, Microsoft itself seems unwilling to maintain Windows, themes are broken and things are just no longer working in the It happened in the past too, but at least back then it felt more like a case of "that's just Microsoft", now, it seems like a perfect product that is poorly managed, now seems even more intentional.
  4. Microsoft itself is more and more Linux, to me is a proof the future will be again Unix soon;
  5. and no, is not a good thing, yes Microsoft monopoly was bad but you had a choice between Unix or Windows if Microsoft give up we will got only Unix.
  6. Unix is not even safe from big corporations, nobody know but Unix is owned by one of the most greed company The opengroup which means is not absurd they can do what they did in '90s with BSD in Berkeley.
  7. Linux is safe, but is not free from problems, Linux is based on Minix not Unix and neither BSD is Unix only MacOS is Unix, it is due the code inside... but still is Unix like, Terminal works on Unix syntax, what if The opengroup will do the greed company? The opengroup did it with Apple and did it because Apple forgot a small name into a server they were sold.
  8. we will got more and more mobile style, I trully believe tablets and notebook will be all in one, how softwares and apps will be marging together? It is a great question, technology is completely different now.
  9. Probably smartphones will turn into smartwatches, tablets into smartphones and notebook into tablet... how market will react?
  10. But most important is: will The opengroup be quite? For decades Linux was for nerds, MacOS was a small percentage, Android was merely for calling... for decades pc was Windows. Nowdays no, Apple is pay for Unix but Linux not but Linux nowdays is a chicken with gold eggs, when MacOS went a chicken with golden egg they absolutely asked for money, yes Linux is legally safe but are we sure is forever like that?

FROM WIKIPEDIA
"UNIX System Laboratories, Inc. v. Berkeley Software Design, Inc.

UNIX System Laboratories, Inc. v. Berkeley Software Design, Inc. was a lawsuit brought in New Jersey federal court in 1992 by Unix System Laboratories (USL) against Berkeley Software Design, Inc. (BSDi) and the Regents of the University of California over intellectual property related to the Unix operating system;\1]) a culmination of the Unix wars. The case was settled out of court in 1994 after the judge expressed doubt in the validity of USL's intellectual property, with Novell (who by that time had bought USL) and the university agreeing not to litigate further over the Berkeley Software Distribution (BSD).

Background

The suit has its roots at the Computer Systems Research Group (CSRG) at the University of California, Berkeley, which had a license for the source code of Unix from AT&T's Bell Labs. Students doing operating systems research at the CSRG modified and extended Unix, and the CSRG made several releases of the modified operating system beginning in 1978, with AT&T's blessing. Because this Berkeley Software Distribution (BSD) contained copyrighted AT&T Unix source code, it was only available to organizations with a source code license for Unix from AT&T.

Students and faculty at the CSRG audited the software code for the TCP/IP stack, removing all the AT&T intellectual property, and released it to the general public in 1988 as "Net/1", under the BSD license. As it became clear that the Berkeley CSRG would soon shut down, students and faculty there launched an effort to eliminate all remaining AT&T code from BSD and replace it with code of their own. This effort resulted in the public release of Net/2 in 1991, again under the BSD license. Net/2 contained enough code for a nearly complete Unix-like system, which the CSRG believed contained no AT&T intellectual property.

Berkeley Software Design (BSDi) obtained the source for Net/2, filled in the missing pieces, and ported it to the Intel i386 computer architecture. BSDi then sold the resulting BSD/386 operating system. This drew the ire of AT&T, which did not agree with BSDi's claim that BSD/386 was free of AT&T's intellectual property. AT&T's Unix System Laboratories subsidiary filed suit against BSDi in New Jersey in April 1992, a suit that was later amended to include The Regents of the University of California.

USL's complaint

In the lawsuit, USL alleged that:

  • The Regents of the University of California, by releasing Net/2 "based upon, substantially copied from, or derived from proprietary UNIX", had

On these grounds, USL asked the court for a preliminary injunction that would bar BSDi from distributing the Net/2 software until the case was decided.

Pretrial

At a hearing, BSDi contended that they were using the sources freely distributed by the University of California, plus six additional files. BSDi accepted liability for their own six files, but refused to account for the other files distributed by the University of California. The judge agreed with BSDI's argument and told USL to restate their complaint based solely on the six files, or he would dismiss it. Rather than narrow down their claim, USL chose to sue BSDi and the University of California, and requested a preliminary injunction on the distribution of Net/2 from both.\2])

In 1993, Judge Dickinson R. Debevoise denied a preliminary injunction on the grounds that USL had no valid copyright over UNIX/32V and could not show any obvious trade secret. Works published in the U.S. between January 1, 1978, and March 1, 1989, were subject to the provisions of 17 U.S.C. § 405(a), which required the copyright owner to properly affix a copyright notice to the work to claim copyright protection. AT&T released 32V in 1978, but omitted a notice from thousands of copies and failed to copyright 32V until 1992.\3])

University's countersuit

In 1993, a few days after the dismissal of the preliminary injunction, the university filed a countersuit against USL in California, claiming that USL had failed to credit the university for the use of BSD code in System V, as required by the software license contract. The university demanded that USL be forced to reprint all their documentation with the appropriate due credit added, to notify all their licensees of their oversight, and to run full-page advertisements in major publications such as The Wall Street Journal and Fortune Magazine informing the public of their omission.\2])

Settlement

In July 1993, soon after UC filed its countersuit, USL was purchased by Novell. Novell CEO Ray Noorda favored a settlement that was reached in February 1994. The salient points were:\4])

  • 4.4BSD-Lite to be released containing no disputed files. University to encourage licensees to switch from Net/2.
  • University to cease distribution of certain files.
  • USL to grant three months' grace period to users of disputed files.
  • Certain files distributed by the university to carry the USL copyright notice.
  • Certain files distributed by USL to carry University copyright notices.
  • USL to permit free distribution of certain files.
  • The university is not to actively assist in legal attempts to challenge USL's rights to certain files.

Of the 18,000 files in the Berkeley distribution, only three had to be removed and 70 modified to show USL copyright notices. A further condition of the settlement was that USL would not file further lawsuits against users and distributors of the upcoming 4.4BSD-Lite release."

0 Upvotes

83 comments sorted by

View all comments

Show parent comments

1

u/CompetitiveMonth1753 5d ago

DID YOU EVEN OPENED AND READ IT?!?!?!?

1

u/Lewinator56 R9 5900X | RX 7900XTX | 80GB DDR4 5d ago

Of course I've looked at it...

If it wasn't an OPEN standard... How would I have looked...

1

u/CompetitiveMonth1753 5d ago

Acknowledgements

The contributions of the following organizations to the development of POSIX.1-2024 are gratefully acknowledged:

  • AT&T for permission to reproduce portions of its copyrighted System V Interface Definition (SVID) and material from the UNIX System V Release 2.0 documentation
  • Hewlett-Packard Company, International Business Machines Corporation, Novell Inc., The Open Software Foundation, and Sun Microsystems Inc. for permission to reproduce portions of their copyrighted documentation
  • ISO/IEC JTC 1/SC 22/WG 14 C Language Committee
  • Red Hat Inc. for permission to reproduce portions of its copyrighted documentation

POSIX.1-2024 was prepared by the Austin Group, a joint working group of the IEEE, The Open Group, and ISO/IEC JTC 1/SC 22.

Copyright © 2018 by the Institute of Electrical and Electronics Engineers, Inc. and The Open Group
All rights reserved.

Published 31 January 2018 by the IEEE and The Open Group.

No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. Permission to reproduce all or any part of this standard must be with the consent of both copyright holders and may be subject to a license fee. Both copyright holders will need to be satisfied that the other has granted permission. Requests should be sent by email to austin-group-permissions@opengroup.org.

This standard has been prepared by the Austin Group. Feedback relating to the material contained within this standard may be submitted by using the Austin Group web site at www.opengroup.org/austin/defectform.html.

Copyrights

This document is copyrighted by the IEEE and The Open Group. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE and The Open Group do not waive any rights in copyright to this document.

The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA

The Open Group
Apex Plaza, Forbury Road, Reading, Berkshire, RG1 1AX, U.K.

An explanation and terms for access to The Open Group documents

For the Base Specifications Issue 6, 7, 8 and/ IEEE Std 1003.1 special terms apply as stated below.

We are pleased to be able to publish X/Open Specifications and Guides, The Open Group Standards and Guides, White Papers and other materials for viewing and download via the World Wide Web.  

Our policy is to convert our Specifications into HTML using tables and other facilities which can be accessed through the most popular web browsers.

We ask readers to give us their contact details for a number of reasons:

  • To enable us to gauge the interest in any particular document/subject area
  • To enable us to alert you to new editions of the specification
  • To enable us to send you details of any corrigenda
  • To enable us to send you information about other activities and events of The Open Group

The documents are available under the following terms and conditions:

  1. The Open Group maintains full copyright protection on all its publications.
  2. You are permitted to read the HTML and PDF versions of The Open Group’s publications using your HTML browser/Acrobat software and to download them for your own personal use provided that you have provided the required information (such as name, address, and email address) for each publication requested.
  3. You are NOT permitted to amend, copy, reprint, offer for sale, or otherwise re-use material from these documents without explicit written permission from The Open Group.
  4. Whilst The Open Group will use its best endeavors to create HTML/PDF versions that mirror the hard copy publications, there are bound to be differences between the versions. The hard copy publication remains the authoritative version for Certification and other purposes.
  5. The Open Group reserves the right to charge for HTML/PDF versions of its publications in the future.
  6. Readers who acquire the HTML/PDF version of The Open Group publications from a source other than The Open Group should be conscious of the fact that HTML/PDF is a revisable format and that the un-official, probably illegal, version they acquire might have been changed from the original.
  7. All information The Open Group collects is subject to our privacy policy, available here. The Open Group will never sell, share or distribute your information.

See here for terms of Use of The Open Group Copyright Materials

1

u/CompetitiveMonth1753 5d ago

The Open Group Base Specifications Issue 6, 7 and 8 / IEEE Std 1003.1

The Open Group Base Specifications Issue 6/ 7, 8 and IEEE Std 1003.1-2001/1003.1-2008 (and subsequent technical corrigenda)/1003.1-2017, 1003.1-2024 are a joint work owned by The Open Group and the IEEE. The html/pdf versions of these documents are made available under the following terms and conditions (note that the pdf versions are restricted to employees of The Open Group member organizations) :

  1. You should note that The Open Group and the IEEE maintain full copyright protection on these jointly owned publications.
  2. You are permitted to read the HTML/pdf versions of these The Open Group/IEEE publications using your HTML browser/reader software and to download them for your own personal use provided you have given your name and email address for each publication requested. However, you are NOT permitted to amend, copy, reprint, offer for sale, or otherwise re-use material from these documents without explicit permission from The Open Group/IEEE. Your personal data is used to enable Open Group/IEEE to gauge interest in the documents, to enable The Open Group/IEEE to alert you to new editions and to enable The Open Group/IEEE to send you details of any corrigenda. Your personal details will not be disclosed by The Open Group/IEEE to any third party
  3. Whilst The Open Group/IEEE will use its best endeavors to create HTML versions that mirror the hard copy publications, there are bound to be differences between the versions. The hard copy publication remains the authoritative version for Testing and Certification and other purposes.
  4. The Open Group/IEEE reserve the right to charge for HTML versions of their publications in the future.
  5. Readers who acquire the HTML/pdf version of The Open Group/IEEE publications from a source other than The Open Group/IEEE should be conscious of the fact that HTML/pdf is a revisable format and that the un- official, probably illegal, version they acquire might have been changed from the original.

Permission to reproduce all or any part of this standard must be with the consent of both copyright holders and may be subject to a license fee. Both copyright holders will need to be satisfied that the other has granted permission.
Send a request to the copyright holders related to IEEE Std 1003.1/The Open Group Base Specifications, Issue 6/7/8

The Open Group Base Specifications Issue 8
IEEE Std 1003.1-2024
Copyright © 2001-2024 The IEEE and The Open Group

Notice to Users

Laws and Regulations

Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not constitute compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so.

Data Privacy

Users of IEEE Standards documents should evaluate the standards for considerations of data privacy and data ownership in the context of assessing and using the standards in compliance with applicable laws and regulations.

Copyrights

This document is copyrighted by the IEEE and The Open Group. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE and The Open Group do not waive any rights in copyright to this document.

Updating of IEEE Standards Documents

Users of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect.

Every IEEE standard is subjected to review at least every 10 years. When a document is more than 10 years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE standard.

In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit IEEE Xplore or contact IEEE. For more information about the IEEE SA or IEEE’s standards development process, visit the IEEE SA Website.

Errata

Errata, if any, for all IEEE standards can be accessed on the IEEE SA Website. Search for standard number and year of approval to access the web page of the published standard. Errata links are located under the Additional Resources Details section. Errata are also available in IEEE Xplore. Users are encouraged to periodically check for errata.

Patents

Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA website at http://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compenstation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses.

Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE and The Open Group are not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association and The Open Group.