What changes often in Linux OS?

  • Thread starter Thread starter pairofstrings
  • Start date Start date
  • Tags Tags
    Linux Os
AI Thread Summary
In the discussion about areas in Linux that experience infrequent changes, the focus is on System Programming, Kernel Programming, and Device Driver Programming. The consensus indicates that the base Kernel API remains stable, with traditional kernel functions undergoing minimal modifications. Most changes within the kernel are internal and do not affect user-space code functionality. Notably, the introduction of device-tree support in kernel drivers required significant rewrites for compatibility, highlighting that while some areas may remain stable, others can experience substantial updates. For detailed change history, resources like kernel.org and related documentation are recommended.
pairofstrings
Messages
411
Reaction score
7
TL;DR Summary
Linux has User-Space and Kernel-Space.
Can anyone tell me what the area is in Linux that doesn't change often?
We have System programming, Kernel Programming, Device Driver Programming which one of these are less frequently touched? By "change", I mean, how often -in System Programming or Kernel Programming or Device Driver Programming- the Linux creators modify the definition of function calls like "cdev_add()" or "fork()" or "spinlocks()" or "printk()"?
Thanks.
 
Technology news on Phys.org
Look at https://www.kernel.org/ for the complete history of changes.

One of the largest changes (well worth the effort) was for device-tree in kernel drivers. I had to rewrite a few drivers to be compatible with that.
https://elinux.org/Device_Tree_Reference#Introduction
https://www.kernel.org/doc/html/latest/devicetree/usage-model.html

The base Kernel API is very stable for traditional kernel functions with most internal code changes being transparent to either space code functionality.
https://www.kernel.org/
https://www.kernel.org/doc/htmldocs/kernel-api/
 
  • Like
  • Informative
Likes pbuk, jim mcnamara and PeterDonis
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
I tried a web search "the loss of programming ", and found an article saying that all aspects of writing, developing, and testing software programs will one day all be handled through artificial intelligence. One must wonder then, who is responsible. WHO is responsible for any problems, bugs, deficiencies, or whatever malfunctions which the programs make their users endure? Things may work wrong however the "wrong" happens. AI needs to fix the problems for the users. Any way to...
Back
Top