Void Linux discussion
 help / color / mirror / Atom feed
From: JD Robinson <jdrobi...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: (how to) automount USB ports
Date: Fri, 31 Jul 2015 22:18:07 -0700 (PDT)	[thread overview]
Message-ID: <dfc3e2e2-e02b-4eac-ab78-223d36e09dae@googlegroups.com> (raw)
In-Reply-To: <d3822a5b-25fc-4bb8-98b7-a5b93b09b578@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

In short, DEs like xfce use the UUID to automatically mount the volume at session startup. The settings are different for each de. The "disks" GUI also has a setting for this, but I haven't seen it since I was playing with mint.

I'm not sure how void would be doing anything differently. I wouldn't rely on the generic device names sda sdb, etc, they change according to how the kernel sees them once they're on the bus and enumerated.

I'm sticking with the UUID theory. As for the corner case I mentioned with the flash drives, it was a bit off topic. And I know not to rely on anything being the same that's hot plugged unless it can be positively identified with a UUID or in the case of DEs, UUID or some fingerprinting scheme.

The configuration settings might be found with udev outside of DEs, but I think you'll find them to be generic in an out of the box installation.

Some DEs look for the device at session start or on insertion by monitoring events coming from dbus or udev. It's not really a specific procedure I trust when dealing with identical models though and the phenomenon might not stand up unless there's some other info being taken into consideration like serial numbers ( something unique to each device ).

  parent reply	other threads:[~2015-08-01  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 15:19 Userx Xbw
2015-08-01  4:54 ` JD Robinson
2015-08-01  5:18 ` JD Robinson [this message]
2015-08-01 12:47 ` Userx Xbw

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=dfc3e2e2-e02b-4eac-ab78-223d36e09dae@googlegroups.com \
    --to="jdrobi..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /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;
as well as URLs for NNTP newsgroup(s).