A system and method for mounting multiple devices on an SLR enable information handling system is disclosed herein. A drive-letter may be assigned to a first user session in a first user session namespace only. A second user may have access to the same drive-letter as the mounting of drive-letters is specific to each specific user session and not the global namespace. A symbolic link is created for each assigned drive-letter and the corresponding drive-letter in the global namespace is deleted allowing for more than the standard mounting of only twenty-six different devices.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: enabling a session level restriction (SLR); receiving a request from a first user of a first client to mount a device connected to the first client; creating a volume for the connected device; determining if a first drive-letter for the volume has been created; retrieving a unique ID for the volume; caching information related to the first drive-letter; deleting the first drive-letter from global namespace; creating a first symbolic link in a first user session namespace based, at least in part, on the cached information, wherein the symbolic link is a second drive-letter; and notifying a manager that the first symbolic link has been created.
This method enables the assignment of unique drive letters to devices within individual user sessions, preventing conflicts across users. It begins by activating a **session-level restriction (SLR)**. When a user on a client computer requests to mount a connected device, a volume is created for it. If a default global drive letter has been assigned to this volume, information about it is cached. This global drive letter is then **deleted from the system's global namespace**. In its place, a **symbolic link** is created within the requesting user's specific session namespace. This symbolic link functions as the drive letter for the device within that user's session, potentially reusing the same letter that was removed globally. This ensures that different users can utilize the same drive letter for distinct devices without conflict. Finally, a system manager is informed that the session-specific symbolic link has been established. ERROR (embedding): Error: Failed to save embedding: Could not find the 'embedding' column of 'patent_claims' in the schema cache
2. The method of claim 1 , further comprising: verifying that the first drive-letter is available for mounting in a second user session namespace.
The method described previously verifies that the initial drive letter is available for mounting in a separate user session namespace before proceeding with the symbolic link creation within the first user's session. This allows the same drive letter to be used by different users without conflict.
3. The method of claim 1 , further comprising: queuing the first symbolic link to be deleted when the connected device is removed.
The method described previously also queues the symbolic link for deletion when the corresponding connected device is removed from the system. This ensures that the user session namespace is cleaned up when the device is no longer available.
4. The method of claim 1 , further comprising: receiving a device removal notification; caching the information; and notifying a first auxiliary application to delete the first symbolic link from the first user session namespace.
The method described previously responds to device removal notifications by caching relevant information and then notifying an auxiliary application to delete the corresponding symbolic link from the user's session namespace.
5. The method of claim 1 , further comprising: receiving a device removal notification; caching the information; deleting the first symbolic link from the first user session namespace; and notifying the manager that the first symbolic link has been deleted.
The method described previously handles device removal by receiving a notification, caching information, deleting the symbolic link from the user's session namespace, and then notifying a manager that the symbolic link has been deleted.
6. The method of claim 1 , wherein the connected device is a mass storage device.
In the method described previously, the connected device being mounted is a mass storage device, such as a USB drive or external hard drive.
7. The method of claim 1 , wherein the symbolic link is created by a second auxiliary application.
In the method described previously, a second auxiliary application is responsible for creating the symbolic link within the user session namespace.
8. The method of claim 7 , further comprising: receiving a removal notification; retrieving the information from an SLR driver; spawning a process in a first user session associated with the first user session namespace; and deleting, by the second auxiliary application, the first symbolic link from the first user session namespace.
The method involving a second auxiliary application creating the symbolic link includes receiving a removal notification, retrieving information from an SLR driver, spawning a process within the user's session namespace, and then instructing the second auxiliary application to delete the corresponding symbolic link from the session namespace.
9. The method of claim 1 , wherein priority is given to the first symbolic link associated with the first user session namespace.
In the method described previously, the symbolic link created within the user session namespace takes priority over any global namespace drive letter assignments, ensuring that the user session's device mapping is correctly resolved.
10. The method of claim 1 , further comprising: receiving a request from a second user of a second client to mount a device connected to the second client; creating a second volume for the second connected device; determining if a second symbolic link for the second volume has been created, wherein the second symbolic link is a third drive-letter; retrieving a second unique ID for the second volume, wherein the third drive-letter is the same as the second drive-letter; caching second information related to the third drive-letter; deleting the third drive-letter from the global namespace; and notifying the manager when the second symbolic link has been created.
The method described previously also supports multiple users by receiving a mount request from a second user for a device. A second volume is created, and it is verified if a symbolic link (a drive letter) already exists. The volume's unique ID is retrieved, and info about the requested drive letter, which is the SAME drive letter as the first user, is cached. This drive letter is removed from the global namespace, and the manager is notified of the second symbolic link's creation. Each user effectively has the same drive letter, but it's unique to their session.
11. One or more computer-readable non-transitory storage media embodying logic that is operable when executed to: by an operating system: enabling a session level restriction (SLR); receiving a request from a first user of a first client to mount a device connected to the first client; creating a volume for the connected device; determining if a first drive-letter for the volume has been created; retrieving a unique ID for the volume; caching information related to the first drive-letter; deleting the first drive-letter from global namespace; creating a first symbolic link in a first user session namespace based, at least in part, on the cached information, wherein the first symbolic link is a second drive-letter; and notifying a manager that the first symbolic link has been created.
Computer-readable storage media contains instructions that, when executed by an operating system, enable session level restrictions (SLR), receive a device mount request from a user, create a volume, determine if the drive letter exists, retrieve a unique ID, cache information, delete the drive letter from the global namespace, create a symbolic link in the user's session namespace using cached information (the symbolic link being a new drive letter), and notify a manager that the symbolic link has been created.
12. The media of claim 11 , further comprising: by the operating system: verifying that the first drive-letter is available for mounting in a second user session namespace; and queuing the first symbolic link to be deleted when the connected device is removed.
The media from the previous description further instructs the operating system to verify that the drive letter is available in another user's session namespace, and queues the symbolic link for deletion when the connected device is removed.
13. The media of claim 11 , further comprising: by an operating system: receiving a device removal notification; caching the information; deleting the first symbolic link from the first user session namespace; and notifying the manager that the first symbolic link has been deleted.
The media from the previous description also instructs the operating system to receive a device removal notification, cache related information, delete the symbolic link from the user's session namespace, and notify the manager that the symbolic link has been deleted.
14. The media of claim 11 , wherein the first symbolic link is created by a second auxiliary application.
On the media from the previous description, a second auxiliary application is responsible for creating the symbolic link.
15. The media of claim 14 , further comprising: by the operating system: receiving a removal notification; retrieving the information from an SLR driver; spawning a process in a first user session associated with the first user session namespace; deleting the second drive-letter from the first user session namespace; deleting, by the second auxiliary application, the first symbolic link.
On the media where a second auxiliary application creates the symbolic link, the operating system receives a removal notification, retrieves information from an SLR driver, spawns a process in the user session, deletes the secondary drive letter (symbolic link) from the user session namespace, and instructs the second auxiliary application to delete the original symbolic link.
16. The media of claim 11 , further comprising: by the operating system: receiving a request from a second user of a second client to mount a device connected to the second client; creating a second volume for the second connected device; determining if a second symbolic link for the second volume has been created, wherein the second symbolic link is a third drive-letter; retrieving a second unique ID for the second volume, wherein the third drive-letter is the same as the second drive-letter; caching second information related to the third drive-letter; deleting the third drive-letter from the global namespace; and notifying the manager when the second symbolic link has been created.
The media from the earlier description also handles multiple users. It receives a mount request from a second user, creates a volume, determines if a symbolic link already exists, retrieves the volume's unique ID where the drive letter used is the SAME as the first user, caches information, deletes that drive letter from the global namespace, and notifies the manager that the symbolic link has been created.
17. An information handling system comprising: one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to: by an operating system: enabling a session level restriction (SLR); receiving a request from a first user of a first client to mount a device connected to the first client; creating a volume for the connected device; determining if a first drive-letter for the volume has been created; retrieving a unique ID for the volume; caching information related to the first drive-letter; deleting the first drive-letter from global namespace; creating a first symbolic link in a first user session namespace based, at least in part, on the cached information, wherein the first symbolic link is a second drive letter; and notifying a manager that the first symbolic link has been created.
An information handling system (computer) includes processors and memory with instructions. The processors, when executing instructions, enable session level restrictions (SLR), receive a device mount request from a user, create a volume, determine if the drive letter exists, retrieve a unique ID, cache information, delete the drive letter from the global namespace, create a symbolic link in the user's session namespace using cached information (the symbolic link being a new drive letter), and notify a manager that the symbolic link has been created.
18. The information handing system of claim 17 , further comprising: by the operating system: receiving a device removal notification; caching the information; deleting the first symbolic link from the first user session namespace; and notifying the manager that the first symbolic link has been deleted.
The information handling system previously described handles device removal by receiving a notification, caching information, deleting the symbolic link from the user's session namespace, and then notifying the manager that the symbolic link has been deleted.
19. The information handling system of claim 17 , further comprising: by the operating system: wherein the first symbolic link is created by a second auxiliary application; receiving a removal notification; retrieving the information from an SLR driver; spawning a process in a first user session associated with the first user session namespace; deleting the second drive-letter from the first user session namespace; and deleting, by the second auxiliary application, the first symbolic link.
The information handling system from the earlier description, where a second auxiliary application creates symbolic links, handles device removal by receiving a notification, retrieving information from the SLR driver, spawning a process in the user session, deleting the second drive letter (symbolic link) from the user session namespace, and instructing the second auxiliary application to delete the original symbolic link.
20. The information handling system of claim 17 , further comprising: by the operating system: receiving a request from a second user of a second client to mount a device connected to the second client; creating a second volume for the second connected device; determining if a second symbolic link for the second volume has been created, wherein the second symbolic link is a third drive-letter; retrieving a second unique ID for the second volume, wherein the third drive-letter is the same as the second drive-letter; caching second information related to the third drive-letter; deleting the third drive-letter from the global namespace; and notifying the manager that the second symbolic link has been created.
The information handling system previously described handles multiple users. It receives a mount request from a second user, creates a volume, determines if a symbolic link already exists, retrieves the volume's unique ID where the drive letter used is the SAME as the first user, caches information, deletes that drive letter from the global namespace, and notifies the manager that the symbolic link has been created.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
January 12, 2015
May 2, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.