浏览代码

Documentation: Change references to uid based sockets to sids

Peter Elliott 2 年之前
父节点
当前提交
37f527be9c
共有 2 个文件被更改,包括 4 次插入5 次删除
  1. 3 4
      Base/usr/share/man/man7/Audio-subsystem.md
  2. 1 1
      Documentation/Browser/ProcessArchitecture.md

+ 3 - 4
Base/usr/share/man/man7/Audio-subsystem.md

@@ -1,6 +1,6 @@
 ## Name
 ## Name
 
 
-Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces. 
+Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces.
 
 
 ## Description
 ## Description
 
 
@@ -18,9 +18,8 @@ AudioServer is responsible for handling userland audio clients and talking to th
 application should ever need to write to a device in `/dev/audio` directly, except for special cases in which
 application should ever need to write to a device in `/dev/audio` directly, except for special cases in which
 AudioServer is not present.
 AudioServer is not present.
 
 
-As with all system servers, AudioServer provides an IPC interface on `/tmp/user/%uid/portal/audio`, with `%uid` being
-the uid
-of the current user. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source
+As with all system servers, AudioServer provides an IPC interface on `/tmp/session/%sid/portal/audio`, with `%sid` being
+the current login session id. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source
 of information. For controlling mixer functionality, clients have the ability to obtain and change their own volume, or
 of information. For controlling mixer functionality, clients have the ability to obtain and change their own volume, or
 the main volume and mute state.
 the main volume and mute state.
 
 

+ 1 - 1
Documentation/Browser/ProcessArchitecture.md

@@ -31,7 +31,7 @@ This process can decode images (PNG, JPEG, BMP, ICO, PBM, etc.) into bitmaps. Ea
 ### How processes are spawned
 ### How processes are spawned
 
 
 To get a fresh **WebContent** process, anyone with the suitable file system permissions can spawn one by connecting to
 To get a fresh **WebContent** process, anyone with the suitable file system permissions can spawn one by connecting to
-the socket at `/tmp/user/%uid/portal/webcontent`, with `%uid` being the uid of the current user. This socket is managed
+the socket at `/tmp/user/%sid/portal/webcontent`, with `%sid` being the current login session id. This socket is managed
 by **
 by **
 SystemServer** and will spawn a new instance of **WebContent** for every connection.
 SystemServer** and will spawn a new instance of **WebContent** for every connection.