Page 1 of 1

Intrusive behavior of the automounting feature

Posted: Sun Nov 27, 2016 5:40 am
by kraileth
My system was installed as GhostBSD 10.3 MATE and I upgraded it to 11.0-RELEASE doing a source upgrade. All packages were rebuilt from ports using the latest versions of course. MATE hasn't been touched for a while in FreeBSD, so I guess that this information is not that important but I wanted to give it anyway.

I'm having problems with the automounting of USB drives. I have a USB key that has GhostBSD11.0-PREALPHA2 on it as I wanted to try that out. I didn't have time for it, yet, and later decided that I'd rather give the Xfce edition of GhostBSD a spin to see what that's like. When I insert the USB key, I'm getting these four error boxes:

Image
(Please click to enlarge)

That's fine as these are not common filesystems, I guess. The problem however is not that these cannot be mounted - the problem is that the EFI partition is being mounted. And not only is it mounted once (which would be ok), but it is remounted automatically if I unmount it!

It doesn't really matter if I unmount it graphically in Caja like this:

Image

or if I do a sudo umount /media/disk/, the result is the same: All partitions from the USB key disappear for a second and then I'm back at the beginning, getting the messages from the first picture again.

This is definitely not the expected behavior that I know from MATE on other systems. Normally media should not be automatically re-mounted unless the USB key was removed and re-attached in between. I have been able to dd another image on it by preparing the command in the terminal, clicking unmount and pressing ENTER on the terminal quickly enough.

BTW: That strange behavior does not occur if I attach another USB key with a regular FreeBSD image on it.

Any clues on what's happening here? I can cope with it as it is now but since I intend to test new GhostBSD alphas, betas and RCs now and then, it's still a bit of an annoying bug. So any help would be appreciated.

Re: Intrusive behavior of the automounting feature

Posted: Mon Nov 28, 2016 4:11 am
by ASX
the automounter in the current form is definitely intrusive, I have disabled it log ago, by turning off "hald" in rc.conf:

Code: Select all

hald_enable="NO"
fact is that we were already aware of that, in fact we disabled hald when performing the installation from live media, and in our bug tracker there is an "issue" specifically t
o remove hal support completely.

Re: Intrusive behavior of the automounting feature

Posted: Mon Nov 28, 2016 12:01 pm
by kraileth
ASX wrote:the automounter in the current form is definitely intrusive, I have disabled it log ago, by turning off "hald" in rc.conf:

Code: Select all

hald_enable="NO"
fact is that we were already aware of that, in fact we disabled hald when performing the installation from live media, and in our bug tracker there is an "issue" specifically t
o remove hal support completely.
I've never heard good things about HAL and it seems like everybody is looking to finally do away with it... So that's HAL's fault, too? Thanks for clearifying that! :)

Re: Intrusive behavior of the automounting feature

Posted: Mon Nov 28, 2016 4:45 pm
by ASX
I don't know if it is HAL fault, most likely a bad interaction between HAL and other components ...
Anyway, FreeBSD (and this GhostBSD) should use devd + some other components ... devd is already up and running ... we need time to delve into the whole ...