Re: [arch-general] [arch-dev-public] [RFC] the future of /media
There are very good reasons for this change (mainly security),
I think it had very little to do with security, unless you count device type privacy information from folder names. I use /media/usb? and they are accessible only by root and whichever user mounted it, logically findable by order of mount. I believe the reason was so that it was in a filesystem meant for dynamic files (this feature is really irritating for some default labels but I guess a little prettier otherwise and for multi-seat). I have udisks 1 and 2 installed but use neither. I have permanent folders in /media/. Will /media/ changes by pacman simply fail and everything continue happily or will I simply have to recreate or make them immutable? -- _______________________________________________________________________ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) _______________________________________________________________________
On Thu, Nov 22, 2012 at 5:23 PM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
I have udisks 1 and 2 installed but use neither. I have permanent folders in /media/. Will /media/ changes by pacman simply fail and everything continue happily or will I simply have to recreate or make them immutable?
As long as either udisks1 is installed or /media is not empty, pacman will not touch it.
On Fri, 23 Nov 2012 00:12:11 +0100 Tom Gundersen <teg@jklm.no> wrote:
On Thu, Nov 22, 2012 at 5:23 PM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
I have udisks 1 and 2 installed but use neither. I have permanent folders in /media/. Will /media/ changes by pacman simply fail and everything continue happily or will I simply have to recreate or make them immutable?
As long as either udisks1 is installed or /media is not empty, pacman will not touch it.
A bit off-topic... do I understand correctly that /run/media is created dynamically by udisks2 whenever it is started? -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
participants (3)
-
Kevin Chadwick
-
Leonid Isaev
-
Tom Gundersen