1 |
On Thu, 3 May 2012 20:33:19 -0400 |
2 |
Joshua Murphy <poisonbl@×××××.com> wrote: |
3 |
|
4 |
> On Thu, May 3, 2012 at 7:00 PM, walt <w41ter@×××××.com> wrote: |
5 |
> > On 05/03/2012 02:48 PM, Canek Peláez Valdés wrote: |
6 |
> >> On Thu, May 3, 2012 at 3:18 PM, walt <w41ter@×××××.com> wrote: |
7 |
> >>> On 04/13/2012 05:19 PM, walt wrote: |
8 |
> >>>> |
9 |
> >>>> A recent update |
10 |
> >>>> (udev?) on my ~amd64 machines is now mounting removable drives |
11 |
> >>>> on /run/media instead of /media. |
12 |
> >>> |
13 |
> >>> |
14 |
> >>> Ha! I should have suspected Lennart from the beginning: |
15 |
> >>> |
16 |
> >>> http://cgit.freedesktop.org/systemd/systemd/commit/?id=231931ffba1bca9d8759bbd6f797e56f8c6971fa |
17 |
> >> |
18 |
> >> The link you posted has nothing to do with this; that's only a |
19 |
> >> systemd-specific change in response to a change in udisks2. In |
20 |
> >> other words, Lennart has nothing to do with this change, the |
21 |
> >> responsible is David Zeuthen, udisks2 maintainer: |
22 |
> >> |
23 |
> >> https://plus.google.com/u/0/110773474140772402317/posts/NqPUifsFUYH |
24 |
> > |
25 |
> > Thanks for the correction. |
26 |
> > |
27 |
> >> And it's actually a pretty reasonable change (IMHO): now in |
28 |
> >> multiseat configurations each user can plug a USB drive and only |
29 |
> >> him/she will see it |
30 |
> > |
31 |
> > I've thought that for a long time. Mounting my own "personal |
32 |
> > mount" on a system directory never made any sense to me. |
33 |
> > However, /run/media is still a system directory, so it still |
34 |
> > doesn't make any sense to me. |
35 |
> > |
36 |
> > I think /home/wa1ter/media is a more logical choice. But I'm not |
37 |
> > doing the coding in this bazaar ;) |
38 |
> > |
39 |
> > The upstream dev(s) seem intent on mounting removable media on a |
40 |
> > tempfs for some reason. Do you know why? |
41 |
> > |
42 |
> > I understand completely the reason for inventing /run and making it |
43 |
> > a tempfs (I think Lennart *was* involved in that), but why use /run |
44 |
> > when it's not necessary or (IMHO) logical? |
45 |
> |
46 |
> In my completely uninformed guess... a) tmpfs automatically 'cleans |
47 |
> up' every reboot, making sure old folders aren't sitting around stale |
48 |
> even if something did go wrong, and/or b) it's guaranteed writable for |
49 |
> the service that needs to make those mount points. I could probably |
50 |
> come up with a 'c', but I'd likely have to actually do a bit of |
51 |
> reading on the topic before rising looking even more foolishly un-read |
52 |
> on the topic than I already do! :-P |
53 |
> |
54 |
|
55 |
Here you go, one time c): |
56 |
|
57 |
/run can be guaranteed to exist immediately after / is mounted, which |
58 |
fixes a whole slew of really horrible problems if it isn't. |
59 |
|
60 |
|
61 |
|
62 |
-- |
63 |
Alan McKinnnon |
64 |
alan.mckinnon@×××××.com |