public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Dahlin <cjdahlin@ncsu.edu>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Josh Boyer <jwboyer@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: USB Key light on/off state depending on mount
Date: Fri, 07 Sep 2007 15:56:58 -0400	[thread overview]
Message-ID: <46E1AD0A.3080006@ncsu.edu> (raw)
In-Reply-To: <46D0AB7B.1080709@s5r6.in-berlin.de>

Sorry to have left this dormant for so long.

Running eject in either of the ways suggested still leaves the light on 
my particular key turned on.

Stefan Richter wrote:
> Guennadi Liakhovetski wrote:
>   
>> I might imagine how windows turns the LED off on 
>> unmount. Try "eject /dev/sdX", where sdX is your USB storage, after you 
>> unmount it. Be careful, especially if you have SATA (or SCSI) discs in 
>> your system or if you use libata for PATA discs not to eject the wrong 
>> one...
>>     
>
> If there is only one USB disk connected:
> # eject /dev/disk/by-path/*usb*:0
>
> Provided you let udev create links for you.  BTW, the /dev/disk/by-id/
> symlinks are nice for static mount points in /etc/fstab.
>
> After a disk was mounted, eject also accepts the mountpoint as parameter
> and will unmount the disk before it tries to eject it.
>   


  reply	other threads:[~2007-09-07 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 20:58 USB Key light on/off state depending on mount Casey Dahlin
2007-08-24 21:13 ` Josh Boyer
2007-08-25 19:26   ` Guennadi Liakhovetski
2007-08-25 22:21     ` Stefan Richter
2007-09-07 19:56       ` Casey Dahlin [this message]
2007-08-26 10:10     ` Xavier Bestel
     [not found] <fa.BwCgwGvTNIOD+KEeBrvP11xCEmw@ifi.uio.no>
2007-08-24 23:19 ` Robert Hancock
2007-08-25 10:49   ` James Bruce
2007-08-25 11:58     ` Éric Piel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46E1AD0A.3080006@ncsu.edu \
    --to=cjdahlin@ncsu.edu \
    --cc=g.liakhovetski@gmx.de \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox