Autosave: 2024-10-24 17:28:58

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/385af4b4_Baran_distributed_networks.md

@@ -3,7 +3,7 @@ tags: [fleeting, networks, ARPANET, packet-switching]
 created: Tuesday, October 22, 2024
 ---
 
-# 385af4b4-Baran_distributed_networks
+# 385af4b4_Baran_distributed_networks
 
 ## Paul Baran's concept of a distributed network and influence on architecture of the ARPANET
 

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/Threads.md

@@ -31,10 +31,10 @@ utilise threads.
 
 ## Hardware considerations
 
-Each [processor core](./CPU_architecture.md) can only run one thread at a time
+Each [processor core](CPU_architecture.md) can only run one thread at a time so
-so the number of cores that a device's CPU has deterimines how many threads can
+the number of cores that a device's CPU has deterimines how many threads can run
-run at once. In practice, then, the CPU shuffles between multiple threads in
+at once. In practice, then, the CPU shuffles between multiple threads in
-[clock segments](./Clock_signals.md). This is known as scheduling and is managed
+[clock segments](Clock_signals.md). This is known as scheduling and is managed
 by the process that the thread belongs to.
 
 ## Related notes

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/cfbef1c4_web_precursors.md

@@ -13,7 +13,7 @@ Example services: checking one's bank balance, paying bills, transferring money,
 booking holidays.
 
 (Presumably, the services would be hosted on a providers'
-[mainframe](./Mainframe_computers.md) or mini-computer, which the consumer would
+[mainframe](Mainframe_computers.md) or mini-computer, which the consumer would
 access through something like time-sharing?)
 
 ![BT telephone modem](static/modem-bt.png)

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/e470bf3d_IMPs_in_the_ARPANET.md

@@ -3,10 +3,10 @@ tags: [ARPA, ARPANET, networks, computer-history]
 created: Friday, October 18, 2024
 ---
 
-# e470bf3d-IMPs_in_the_ARPANET
+# e470bf3d_IMPs_in_the_ARPANET
 
 Within the #ARPANET, IMPs (Information Message Processors) were nodes
-distinguished from [hosts](./Network_hosts.md). They were computers designed to
+distinguished from [hosts](Network_hosts.md). They were computers designed to
 receive and route the the packets from one host to another, described as
 "adaptive routing".
 
@@ -20,7 +20,7 @@ Their job was to:
 - confirm successful transmission
 
 These responsibilities required the IMP to "know" the location and addresses of
-other IMPs and hosts on the [network](./Network_fundamentals.md) and their
+other IMPs and hosts on the [network](Network_fundamentals.md) and their
 proximity to them.
 
 From the point of view of the host user, the existence of the IMPs would be

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/f0f70a3c_ARPANET_motivations.md

@@ -3,14 +3,14 @@ tags: [ARPA, ARPANET, networks, computer-history]
 created: Friday, October 18, 2024
 ---
 
-# f0f70a3c-ARPANET-motivations
+# f0f70a3c_ARPANET_motivations
 
 It is inaccurate to say that the chief motivation in creating the ARPANET was to
 create a network that could withstand nuclear conflict, where mulitple nodes
 could be hit and the network could still go on functioning.
 
 Ideas that originated from this concern _did_ influence the project (chiefly
-[Paul Baran's work on distributed networks](./385af4b4_baran_distributed_networks.md)
+[Paul Baran's work on distributed networks](385af4b4_baran_distributed_networks.md)
 at RAND), but this was not the concern of the ARPANET.
 
 ARPA's objectives were focused more on reducing efficiency in the academic and

neuron/e64d42b7-6034-467b-be10-f60f7ae23656/index.md

@@ -13,20 +13,20 @@ computer science.
 
 ![not-by-ai-badge](static/not-by-ai-alternative--light.svg)
  
-**Build ID:** 85c93482-be2b-476d-8d37-e67e35658655
+**Build ID:** e64d42b7-6034-467b-be10-f60f7ae23656
 
-**Published:** Thu 24 Oct 2024 07:31:51
+**Published:** Thu 24 Oct 2024 17:28:56
 
 ### Recent edits 
 
 - [[cfbef1c4_web_precursors]] 
-- [[861cc26e_ARPA_origins]] 
-- [[f0f70a3c_ARPANET_motivations]] 
 - [[e470bf3d_IMPs_in_the_ARPANET]] 
+- [[f0f70a3c_ARPANET_motivations]] 
+- [[Threads]] 
 - [[385af4b4_Baran_distributed_networks]] 
+- [[861cc26e_ARPA_origins]] 
 - [[Compile_Python_app_to_single_executable]] 
 - [[VirtualMemory]] 
-- [[Zero_property_of_multiplication]] 
 
 
 ### All notes (466) 

zk/385af4b4_Baran_distributed_networks.md

@@ -3,7 +3,7 @@ tags: [fleeting, networks, ARPANET, packet-switching]
 created: Tuesday, October 22, 2024
 ---
 
-# 385af4b4-Baran_distributed_networks
+# 385af4b4_Baran_distributed_networks
 
 ## Paul Baran's concept of a distributed network and influence on architecture of the ARPANET
 

zk/Threads.md

@@ -31,10 +31,10 @@ utilise threads.
 
 ## Hardware considerations
 
-Each [processor core](./CPU_architecture.md) can only run one thread at a time
+Each [processor core](CPU_architecture.md) can only run one thread at a time so
-so the number of cores that a device's CPU has deterimines how many threads can
+the number of cores that a device's CPU has deterimines how many threads can run
-run at once. In practice, then, the CPU shuffles between multiple threads in
+at once. In practice, then, the CPU shuffles between multiple threads in
-[clock segments](./Clock_signals.md). This is known as scheduling and is managed
+[clock segments](Clock_signals.md). This is known as scheduling and is managed
 by the process that the thread belongs to.
 
 ## Related notes

zk/cfbef1c4_web_precursors.md

@@ -13,7 +13,7 @@ Example services: checking one's bank balance, paying bills, transferring money,
 booking holidays.
 
 (Presumably, the services would be hosted on a providers'
-[mainframe](./Mainframe_computers.md) or mini-computer, which the consumer would
+[mainframe](Mainframe_computers.md) or mini-computer, which the consumer would
 access through something like time-sharing?)
 
 ![BT telephone modem](../img/modem-bt.png)

zk/e470bf3d_IMPs_in_the_ARPANET.md

@@ -3,10 +3,10 @@ tags: [ARPA, ARPANET, networks, computer-history]
 created: Friday, October 18, 2024
 ---
 
-# e470bf3d-IMPs_in_the_ARPANET
+# e470bf3d_IMPs_in_the_ARPANET
 
 Within the #ARPANET, IMPs (Information Message Processors) were nodes
-distinguished from [hosts](./Network_hosts.md). They were computers designed to
+distinguished from [hosts](Network_hosts.md). They were computers designed to
 receive and route the the packets from one host to another, described as
 "adaptive routing".
 
@@ -20,7 +20,7 @@ Their job was to:
 - confirm successful transmission
 
 These responsibilities required the IMP to "know" the location and addresses of
-other IMPs and hosts on the [network](./Network_fundamentals.md) and their
+other IMPs and hosts on the [network](Network_fundamentals.md) and their
 proximity to them.
 
 From the point of view of the host user, the existence of the IMPs would be

zk/f0f70a3c_ARPANET_motivations.md

@@ -3,14 +3,14 @@ tags: [ARPA, ARPANET, networks, computer-history]
 created: Friday, October 18, 2024
 ---
 
-# f0f70a3c-ARPANET-motivations
+# f0f70a3c_ARPANET_motivations
 
 It is inaccurate to say that the chief motivation in creating the ARPANET was to
 create a network that could withstand nuclear conflict, where mulitple nodes
 could be hit and the network could still go on functioning.
 
 Ideas that originated from this concern _did_ influence the project (chiefly
-[Paul Baran's work on distributed networks](./385af4b4_baran_distributed_networks.md)
+[Paul Baran's work on distributed networks](385af4b4_baran_distributed_networks.md)
 at RAND), but this was not the concern of the ARPANET.
 
 ARPA's objectives were focused more on reducing efficiency in the academic and