PSF: Append @notes/personal-software-foundry.org to closos files
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
#+TITLE: CLOSOS: Attributed Object Store
|
#+TITLE: CLOSOS: Attributed Object Store
|
||||||
#+ID: closos-attributed-object-store
|
#+ID: closos-attributed-object-store
|
||||||
#+DATE: 2026-03-22
|
#+DATE: 2026-03-22
|
||||||
#+FILETAGS: :architecture:lisp:os:closos:database:
|
#+FILETAGS: :architecture:lisp:os:closos:database:@notes/personal-software-foundry.org:
|
||||||
|
|
||||||
* Concept
|
* Concept
|
||||||
The traditional hierarchical file system (folders and files) is replaced by a system-wide database of objects retrieved via key/value attributes.
|
The traditional hierarchical file system (folders and files) is replaced by a system-wide database of objects retrieved via key/value attributes.
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
#+TITLE: CLOSOS: Persistence by Default (Single Memory Abstraction)
|
#+TITLE: CLOSOS: Persistence by Default (Single Memory Abstraction)
|
||||||
#+ID: closos-memory-persistence
|
#+ID: closos-memory-persistence
|
||||||
#+DATE: 2026-03-22
|
#+DATE: 2026-03-22
|
||||||
#+FILETAGS: :architecture:lisp:os:closos:persistence:
|
#+FILETAGS: :architecture:lisp:os:closos:persistence:@notes/personal-software-foundry.org:
|
||||||
|
|
||||||
* Concept
|
* Concept
|
||||||
CLOSOS eliminates the distinction between volatile primary memory (RAM) and permanent secondary memory (Disk). Primary memory functions as a transparent cache for a persistent object store.
|
CLOSOS eliminates the distinction between volatile primary memory (RAM) and permanent secondary memory (Disk). Primary memory functions as a transparent cache for a persistent object store.
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
#+TITLE: CLOSOS: Multiple Simultaneous Environments
|
#+TITLE: CLOSOS: Multiple Simultaneous Environments
|
||||||
#+ID: closos-multiple-environments
|
#+ID: closos-multiple-environments
|
||||||
#+DATE: 2026-03-22
|
#+DATE: 2026-03-22
|
||||||
#+FILETAGS: :architecture:lisp:os:closos:security:
|
#+FILETAGS: :architecture:lisp:os:closos:security:@notes/personal-software-foundry.org:
|
||||||
|
|
||||||
* Concept
|
* Concept
|
||||||
CLOSOS supports multiple simultaneous global environments, where an environment is a mapping from names to objects (functions, classes, packages).
|
CLOSOS supports multiple simultaneous global environments, where an environment is a mapping from names to objects (functions, classes, packages).
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
#+TITLE: CLOSOS: Language-Based Protection Mechanisms
|
#+TITLE: CLOSOS: Language-Based Protection Mechanisms
|
||||||
#+ID: closos-protection-mechanisms
|
#+ID: closos-protection-mechanisms
|
||||||
#+DATE: 2026-03-22
|
#+DATE: 2026-03-22
|
||||||
#+FILETAGS: :architecture:lisp:os:closos:security:
|
#+FILETAGS: :architecture:lisp:os:closos:security:@notes/personal-software-foundry.org:
|
||||||
|
|
||||||
* Concept
|
* Concept
|
||||||
Security in a Lisp OS is enforced by the compiler and runtime environment rather than traditional hardware MMU (Memory Management Unit) boundaries.
|
Security in a Lisp OS is enforced by the compiler and runtime environment rather than traditional hardware MMU (Memory Management Unit) boundaries.
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
#+TITLE: CLOSOS: Single Address Space Architecture
|
#+TITLE: CLOSOS: Single Address Space Architecture
|
||||||
#+ID: closos-single-address-space
|
#+ID: closos-single-address-space
|
||||||
#+DATE: 2026-03-22
|
#+DATE: 2026-03-22
|
||||||
#+FILETAGS: :architecture:lisp:os:closos:
|
#+FILETAGS: :architecture:lisp:os:closos:@notes/personal-software-foundry.org:
|
||||||
|
|
||||||
* Concept
|
* Concept
|
||||||
In a Lisp Operating System (CLOSOS), all applications and the system kernel share one large, unified 64-bit address space.
|
In a Lisp Operating System (CLOSOS), all applications and the system kernel share one large, unified 64-bit address space.
|
||||||
|
|||||||
Reference in New Issue
Block a user