| 1 |
On Tuesday 08 Jan 2013 07:09:40 J. Roeleveld wrote: |
| 2 |
> On Mon, 7 Jan 2013 22:53:19 +0000 |
| 3 |
> |
| 4 |
> Mick <michaelkintzios@×××××.com> wrote: |
| 5 |
> > On Monday 07 Jan 2013 07:35:32 Dale wrote: |
| 6 |
> > |
| 7 |
> > BTW, pressing the touch sensitive button on the laptop to eject the |
| 8 |
> > CD won't work, neither will typing eject in a terminal: |
| 9 |
> > |
| 10 |
> > $ eject |
| 11 |
> > eject: tried to use `/mnt/cdrom' as device name but it is no block |
| 12 |
> > device eject: unable to find or open device for: `cdrom' |
| 13 |
> > |
| 14 |
> > So, eject is still looking for cdrom ... |
| 15 |
> > |
| 16 |
> > Either all commands and legacy apps should update themselves, or I |
| 17 |
> > better follow Mark's suggestion? |
| 18 |
> |
| 19 |
> Mick, |
| 20 |
> |
| 21 |
> You can tell "eject" which device to eject by adding the device-name to |
| 22 |
> the command, eg: |
| 23 |
> # eject /dev/sr0 |
| 24 |
> |
| 25 |
> This also works with USB-drives/sticks :) |
| 26 |
> |
| 27 |
> -- |
| 28 |
> Joost |
| 29 |
|
| 30 |
Yes, of course, otherwise I would be rather stuck, or would have to make |
| 31 |
symlinks, or even boot into MSWindows ... just to eject a CD! |
| 32 |
-- |
| 33 |
Regards, |
| 34 |
Mick |
Archives