Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Sciuriware

macrumors 6502a
Original poster
Jan 4, 2014
856
201
Gelderland
Hello all,
I presume that a majority of the Sonoma users upgraded to Sequoia without a problem.
... or they did not check everything yet.

Well here is my tale:
After upgrading my laptop to 15.1 initially everything seemed to work fine.
I must admit that I'm using quite well-known 3rd party applications, like
FireFox, Thunderbird, Eclipse, MacVim, ShutterEncoder, Audacity, CCC, JAVA, VLC, Skim ...

But my own applications, written in JAVA gave severe problems.
I use to run the same applications on several systems and to control
their local behaviour, I use the system's node name.

It turned out that Sequoia does strange things with "/bin/hostname" (a reliable source, I thought).
On my laptop the name suddenly changed into "Mac" when WIFI was enabled.
On my desktop this did NOT happen, but when I disconnected the Ethernet
UTP wire, the hostname suddenly was appended by ".local"

Solution: each of my machines now has a little text file in the /User/Shared area
containing the system's name, which has to be installed only once.

Looking forward to the imminent 15.2 and the unavoidable 16.1, 17.1, 18.1, 19.1 .....
;JOOP!
 
it's an so called apple security feature. when you use WLAN with private mac static your hostname will be mac oder macbookpro. as far as i know WLAN with private mac static is apples default WLAN configuration
 
it's an so called apple security feature. when you use WLAN with private mac static your hostname will be mac oder macbookpro. as far as i know WLAN with private mac static is apples default WLAN configuration
I can live with it. I had to solve so many little things like this over the years, starting with MSWindows 3.
;JOOP!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.