From owner-freebsd-arch Fri Sep 1 1:25: 1 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mtiwmhc24.worldnet.att.net (mtiwmhc24.worldnet.att.net [204.127.131.49]) by hub.freebsd.org (Postfix) with ESMTP id ABD8837B43C; Fri, 1 Sep 2000 01:24:54 -0700 (PDT) Received: from 216.neworleans-05-10rs16rt.la.dial-access.att.net ([12.73.250.216]) by mtiwmhc24.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with SMTP id <20000901082447.JRGO13787.mtiwmhc24.worldnet.att.net@216.neworleans-05-10rs16rt.la.dial-access.att.net>; Fri, 1 Sep 2000 08:24:47 +0000 From: Thrumbar Pathfinder To: freebsd-hardware@FreeBSD.org Cc: arch@FreeBSD.ORG Subject: Auto-Mount/Dismount optional drivers development??? Date: Fri, 01 Sep 2000 03:18:03 -0500 Organization: OmniCorp Interstellar Message-ID: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I propose the following enhancements to the drivers used in FreeBSD. Pleas do not confuse this with that Supermount (supermount) used in ManDrake Linux as this is different entirely... The ability for storage devices to auto-Mount/DisMount their media in the event that the eject button is pushed on the drive itself without executing the dismount command from terminal or by script.. This would help in the following ways : 1. Security : Drives can be linked to ones Login to allow access to only prescribed drives (Media) due to the drive that is not mounted cannot be accessed (drives units are ghost, assigned their ID's but not allowed to mount when the logged on user is not allowed access to it). The drive will appear on a manager to be hazed out to indicate that it is dismounted... This would be more secure than the current use of scripts or manual commands as the code would be securely in the in the driver code. The drive, if possible can also be set to prevent the insertion of media or the removal of said media (some drives can - at least in their Win doze version - when trying to eject and active disk prompt the user and the user select the ignore option thus preventing the ejection from taking place) if possible. Will have to contact drive suppliers to find out if possible... 2. Integrity : This prevents the mistaken removal of media without dismounting first in the event the manual eject is pressed. =09 This also allows for quick change of media for tape or cd jukeboxes with just a click of the drive icon or cd prompt change... 3. Access (see security) The driver would detect the eject command (from the button being pressed - much like current adaptec DirectCD does on my CD-RW drive) and triggers a detection to check it the media is active Active - either of the following a: cancels dismount b: waits for activity to end - dismounts c: halts activity - dismounts d: prompts for action non Active - dismounts media This is for media that does not use a mechanical ejection (Floppy (1.44) but uses and articulated ejection (electrical as in CD's, Zip, Jazz). Including hot-swapable HD's using swap trays (caddies). There is more ways this could be used, but my brain is falling off and I cannot think anymore so I will leave it with the above in hopes another can add their own.. I most likely will not be able to contribute much as I have trouble even spelling the word programming much less doing it (still learning at beginning level).. Any constructive comments?????? Thrumbar@Worldnet.att.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message