Love how Rogers, Bell and Telus are pointing fingers at each other. AFAIK Rogers first stated that they didn’t commit to sharing the infrastructure with Bell and Telus at first, to the surprise and dismay of the TTC. Now Rogers is blaming Bell and Telus for dragging their feet… glad to see the Toronto telco market continues to be an absolute shit show. /s
5 days WFH hands down.
Interesting take. I’ll be making note of this author and reading more of his posts.
Awww I hope she recovers.
Jeez, this is AI generated??? 😳🤯
The fact that the busiest highway in Toronto has sections in such severe state of disrepair is frustrating. Even if that section is under construction, this level of disrepair is inexcusable.
I had a similar issue as you, and switching/reseating DP cables solved it for me. This is the switch I am using.
Also note my monitors can only do 4K@60Hz.
Good point! I assumed the worst; but it’s possible the array is rebuilding or even already rebuilt and just needs to be mounted.
According to LocalSend docs these are the ports that need to be opened: Multicast (UDP) Port: 53317 Address: 224.0.0.167 HTTP (TCP) Port: 53317 AFAIK macOS firewall is app-based, at least in the GUI. So depending on how you installed LocalSend, you may have to add it to the list of allowed apps: https://support.apple.com/en-ca/guide/mac-help/mh34041/mac
You may be able to add the ports above to /etc/pf.conf manually, but AFAIK messing with pf on macOS is not recommended.
The other thing I wanted to ask is about Vallum. If you have it running on that Mac, would it not “take over” the macOS firewall?
Assuming you were using a Linux software RAID, you should be able to recover it.
The first step would be to determine what kind of RAID you were using… btrfs, zfs, mdraid/dmraid/lvm… do you know what kind you set up?
To start the process, try reconnecting your RAID disks to a working Linux machine, then try checking:
- The sudo lsblk command will help you get a list of all connected disks, sizes and partitions.
- The partition tables on the disks, eg: sudo fdisk -l /dev/sda (that’s a lowercase L and /dev/sda is your disk)
- Assuming you use a standard Linux software RAID, try sudo mdadm --examine /dev/sda1. If all goes well, the last command should give you an idea of what state the disk is in, what RAID level you had, etc.
- Next, I would try and see if mdadm can figure out how to reassemble the array, so try sudo mdadm --examine --scan. That should hopefully produce output with the name of the RAID array block device (eg, /dev/md0), RAID level and members of the RAID array (number of disks). Let me know what you discover…
Note: if you used zfs of btrfs, do not do steps 3 and 4; they are MD RAID specific.
Interactive (i.e. end-users) Clients should be using OAuth instead of app passwords. This will allow your users to use their own Office365 credentials for SMTP.
For servers and non-interactive clients (e.g. copiers/printers/toasters/coffee makers) I would suggest something along the lines here: https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#compare-the-options
Something that calls itself… yeah, no thanks. :)