From owner-freebsd-hackers Wed Nov 1 16:29:44 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA03854 for hackers-outgoing; Wed, 1 Nov 1995 16:29:44 -0800 Received: from multivac.orthanc.com (root@multivac.orthanc.com [204.244.20.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA03849 for ; Wed, 1 Nov 1995 16:29:40 -0800 Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7/8.7) with SMTP id QAA26005 for ; Wed, 1 Nov 1995 16:28:45 -0800 (PST) Message-Id: <199511020028.QAA26005@multivac.orthanc.com> X-Authentication-Warning: multivac.orthanc.com: Host lyndon@localhost didn't use HELO protocol From: Lyndon Nerenberg VE7TCP To: freebsd-hackers@freebsd.org Subject: Automounting CD-ROMs X-Attribution: VE7TCP Date: Wed, 01 Nov 1995 16:28:44 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk Are any of you familiar with the Irix 'mediad' daemon? It's main purpose in life is to handle the CDROM automount scenario being discussed. The program refers to a config file listing the devices to be scanned, and probes them periodically (I think every five seconds) to look for media insertion. If a CDROM appears, and if it contains a recognized filesystem, the filesystem is mounted automatically at a location also specified in the config file. It locks the device to prevent a front-panel ejection of the media. Graceful unmount and eject is handled by the 'eject' command. The downside is that 'eject' requires root priv's. If you have a public workstation environment you would want the console user to be able to remove the media they inserted. Determining the class "console user" in a windowing environment could be problematic. Then again, the public workstation scenario usually sees the workstation configured to deny remote logins, so it probably doesn't matter. Just more food for thhought. The AMD scenario seems needlessly complex. --lyndon