Re: MacOS Sequoia vs. Linux Mint

On Sat, 14 Dec 2024 10:31:16 -0500, -hh <recscuba_google@huntzinger.com>
wrote in <vjk8c4$6us$3@dont-email.me>:

On 12/13/24 4:56 PM, vallor wrote:

On 13 Dec 2024 15:40:28 GMT, vallor <vallor@cultnix.org> wrote in
<ls32rcFprp3U1@mid.individual.net>:
 

So upgraded the Mac Studio to Sequoia:
>
$ uname -a
Darwin Mac 24.2.0 Darwin Kernel Version 24.2.0:
Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020 arm64
>
After the initial upgrade from Sonoma, it still had updates
to apply.  This took a while, and included the need for
another reboot -- all to update some xcode crap.
>
It's a lot easier to update Linux than Windows or MacOS.  Why
it would be such a pain for MacOS to do a simple update, I can
only guess at.

 
Perhaps because you're DIYing it from the command line instead of using
the GUI?

Nope, did that all from the gui.

 
For the latter, system can auto-update, whereupon you just get a
notification of "do it tonight, or install now?" whereupon the click
will take you to a license agreement to click and off it goes.
 
Of course, one will need to remember to not have open/unsaved files
which will automatically prevent data loss by pausing any reboots
if/when merited.

What I'd like is for it to download the updates and have them ready
for such an action.  But it _still_ took an inordinate amount of time
to update.  (I didn't complain about the update from Sonoma to Sequoia
because I would expect that to take a while -- it's the extra update
afterwards that I was complaining about.)

 

(I suspect it may be that MacOS doesn't have a facility
with the simplicity of Linux's ldconfig(8) for updating
shared libraries.)

 
Of course, when stuff gets updated in the background overnight, why
should it bother one if an update takes an extra 15 minutes?
 

Also:
>
_[/Users/scott/path_max]_(scott@Mac)🍏_
$ make use_pathconf
cc -g -O2 -std=c90 -Wall -Werror -pedantic    use_pathconf.c   -o use_pathconf
_[/Users/scott/path_max]_(scott@Mac)🍏_
$ ./use_pathconf
1024
>
It's still 1/4 that of Linux.
>
Although, I did run a find(1) on my fileserver for long pathnames, and
found that the longest was 359 characters...so MacOS would be fine with
that.  Windows?  Not so sure.

 
Went to add a static route to another segment of my network, and
couldn't find a way to do it while keeping the dhcp setup.  In order
to add a persistent route, I had to drop to the command line and
run networksetup(8) with the proper incantation.  Now I can ping
my file server.

 
Sounds odd; I can assign static IPs on my router to individual devices
as I want.

Not related.  The SAN segment is a 10G wired network behind my Linux
workstation -- different /24 network.  The most straightforward way
to tell the Mac Studio about how to get to that network is a static
route.  If the dhcp server were more configurable, there is a dhcp
option to add a route -- but I'm not that lucky to have a smarter
dhcp server.

 Of course, that's different from what comes next:
 

Next, I tried to add a time machine backup destination, but there's
no way to add one by IP address from the gui. 

 
Sure, because the GUI is the mainstream solution, and it leverages a 20
year old zeroconf technology (eg. Bonjour).  That facilitates using DHCP
instead of needing to plug in Static IP assignments.  Of course, you're
free to do things the old fashioned & harder way if you so desire.

The reflector is tying together both broadcast domains.  That _is_ the
easy way to do it -- the "hard" way would be to try to set up the destination
with tmutil(8) from the command line.  On the Linux workstation, all I had
to do is modify avahi-daemon.conf with "enable-reflector=yes" and restart
the service -- after that, the Studio could see the Time Machine broacast[*].

 
 

Was going to try
to set one up with tmutil(8), but realized I should instead set
up an MDNS reflector on the router.  After that, the Mac Studio saw
the file server in the time machine tool, and everything followed from
that.

 
Sounds like some subdomain/VPN isolations were doing what they were
supposed to do, so adding the MDNS reflector was to circumvent?

Two different broadcast[*] domains, so the Mac Studio side wasn't seeing
the Time Machine broadcasts until I enabled the reflection.

[*] Actually, it's multicast, but same idea.

The file server runs Linux:
 
Linux DT 3.10.108 #42962 SMP Mon Aug 19 15:14:28 CST 2024
armv7l GNU/Linux synology_alpine_ds2015xs

 
IIRC, same.

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.12.4 Release: Mint 21.3 Mem: 258G
   "Put on your seatbelt. I'm gonna try something new."