Last Sync: 2022-09-18 16:00:05
This commit is contained in:
parent
2e7c688716
commit
bcd0b543b8
3 changed files with 3 additions and 3 deletions
|
@ -14,7 +14,7 @@ So current is the flow of electrons. Charge is the quantity that flows.
|
|||
|
||||
## Why current exists
|
||||
|
||||
Current exists because of the [first law of electrostatics](/Electronics/Physics_of_electricity/Coulombs_Law.md).
|
||||
Current exists because of the [first law of electrostatics](/Electronics/Physics_of_electricity/Coulombs_Laws.md).
|
||||
|
||||
When there is an excess of electrons at one terminal (i.e. negatively charged atoms) and a deficiency of electrons at the other terminal (i.e. positively charged atoms), a \*\*difference of potential\_ exists between the two terminals.
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@ brw-rw---- 1 root disk 259, 3 Jun 4 11:00 nvme0n1p3
|
|||
|
||||
> Since device files are files we can interact with them using standard file programs like `ls` and `cat`.
|
||||
|
||||
The [mode](../Programming_Languages/Shell_Scripting/File_permissions_and_execution.md#what-the-output-means) is different from ordinary files. Each device file is prepended with `b, p, c, s` before the standard permissions. These stand for the major types of devices: _block, character, pipe_ and _socket_.
|
||||
The [mode](/Programming_Languages/Shell_Scripting/File_permissions_and_execution.md#what-the-output-means) is different from ordinary files. Each device file is prepended with `b, p, c, s` before the standard permissions. These stand for the major types of devices: _block, character, pipe_ and _socket_.
|
||||
|
||||
<dl>
|
||||
<dt>block</dt>
|
||||
|
|
|
@ -43,7 +43,7 @@ During the context switch from CPU to user space, the kernel allocates memory. I
|
|||
- Managing read-only memory
|
||||
- Allowing for the use of disk space as auxiliary memory
|
||||
|
||||
> Modern CPUs include a [memory management unit](/Hardware/Memory/Virtual_memory_and_the_MMU.md) which provides the kernel with **virtual** memory. In this scenario, memory isn't directly accessed by the process instead it works on the assumption that is has access to the entire memory of the machine and this is then translated into a map that is applied to the real memory and managed by the kernel.
|
||||
> Modern CPUs include a [memory management unit](/Operating_Systems/Virtual_memory_and_the_MMU.md#the-memory-management-unit-mmu) which provides the kernel with **virtual** memory. In this scenario, memory isn't directly accessed by the process instead it works on the assumption that is has access to the entire memory of the machine and this is then translated into a map that is applied to the real memory and managed by the kernel.
|
||||
|
||||
## Device drivers
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue