On Wednesday 13 June 2018, Dr. Nikolaus Klepp wrote: > Am Mittwoch, 13. Juni 2018 schrieb Kate Draven: > > [...] > > > > > --------------------------------------------------------------------- > > > > I agree, it is a pclos thing. They use udisks2. Which is notorious for > > automount problems. I can't uninstall it because trinity is dependant on > > it. I know how to edit the fstab, but would rather not. It's also not > > going to help because it's rarely the same drive twice. This becomes a > > problem when/because I'm working on client drive data recovery. > > Hi! > > You can install "pmount" and purge "udisks2". That's what I did, and it > works (on devuan, that is). > > Nik You're thinking along the same lines as I was. I did have pmount installed but couldn't purge udisks2 as trinity seems to be dependant on it. I'm doing a clean install since I suspect I screwed up somewhere. User error is often the case. I'll update once I've completed some experiments. Kate --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
