I may not be looking in the correct place, but if the network manager is relying on /usr/local/share/networkmgr/net_api.py then it seems to me that there might be something amiss. There are several functions in that file that check for the presence of the wlan0 interface and return an appropriate st...

Okay, I've finally had a few hours to dig deeper - my findings: - the FreeBSD port of Slim does grab some capabilities out of /etc/login.conf, but not the setenv capabity :( See r379608 for more details. - I haven't been able to identify any support in LightDM (original source or FreeBSD port) for t...

I know about cap_mkdb and that was the first thing I checked when the /etc/login.conf didn't work for a desktop session. I have since double checked SSH sessions and both the /etc/login.conf and /etc/profile approaches work as expected for these. So it seems to me that the graphical desktop login pr...

I would rather not rely on X related scripts as I want these environment variables set for SSH logins as well as local desktop sessions.

# $FreeBSD: releng/11.1/etc/profile 208116 2010-05-15 17:49:56Z jilles $ # # System-wide .profile file for sh(1). # # Uncomment this to give you the default 4.2 behavior, where disk # information is shown in K-Blocks # BLOCKSIZE=K; export BLOCKSIZE # # For the setting of languages and character set...

I get the same behaviour with /bin/sh

Thanks for the followup. I'm glad the /etc/profile approach works for you, but it doesn't work for me in either 11.1alpha1 or 10.3

ASX wrote:Try to disable host I/O cache for the time of installation, eventually re-enable that feature upon install completation.

I tried that and the live image boot still hangs at the same point (i.e. screen is identical to screenshot above).

I need to set global environment variables HTTP_PROXY, HTTPS_PROXY and FTP_PROXY so that anything that needs to connect to the internet can do so via the squid proxy on this network, regardless of the logged in user. The most effective way of doing this I've found in FreeBSD is via the setenv capabi...

Changing the storage configuration back to using IDE drives on a PIIX3 chipset (PIIX 4 IDE controller) instead of the SATA configuration appears to resolve this hanging issue but it would be nice to know why a configuration that works in FreeBSD 11.1 doesn't work for GhostBSD...