On Monday 21 November 2005 22:28, Joerg Schilling wrote: > Robert Lunnon <[EMAIL PROTECTED]> wrote: > > My users don't use the command line, they are fugitives from windows. > > They have common problems with the cdrom refusing to eject. It's hard to > > explain to a windows exile that the cd wont eject because there "Might > > be" a file open on it. In some other cases I've seen things get so > > confused that the CD returns an I/O error and no amount of eject commands > > will eject it. I've had to stop the volume manager, and eject it > > manually. You really cant expect a mere mortal to do these things, they > > need easy ways out of these things. > > > > I personally don't see why a read-only media can't be ejected like this, > > after all we live with floppies and other removable disks (eg flash > > drives) that Solaris just can't prevent you from removing. What makes CDs > > so different? . > > Besides, not being able to eject the CD with the eject button is > > counter-intuitive and in my book that just makes it plain wrong from a > > HMI design point of view. > > Before MS Win did start to "support" this, it was the agreeed behavior: > > - Apple _and_ Sun did have a Floppy drive _without_ eject button. > > - CD-ROM drives did just copy this idea and allowed to make the > eject button to "diasppear" (being hidden). > > If you run a command line, you call "eject cdrom". > > If you use a gui, you just push the eject button on the gui. > > So where is your problem?
Because it doesn't always work and when it doesn't work there is no way to know WHY. If it could be made bulletproof, I'd concede it'd be OK but it is far from bulletproof. This would include a notification on the console when someone tries to eject a busy CD. Bob _______________________________________________ opensolaris-discuss mailing list [email protected]
