400ppm? That’s pretty hard water. Your espressos must taste awful. 😣
I’m a computer and open source enthusiast from Toronto, Ontario, Canada.
400ppm? That’s pretty hard water. Your espressos must taste awful. 😣
If you’re that worried, why not run chmod -R u+w .git inside the project dir to “un write-protect” the files, then just ascend to the directory containing the project dir (cd …) and use rm -r without -f?
The force flag (-f) is the scary one, I presume?
I’d take “works perfectly” with a grain of salt. “Doesn’t die and continues to grow after thawing” is more accurate, IMHO.
I wonder if this has anything to do with Apple’s CSAM scanning. You know, hang on to the photos as evidence, and, for an added bonus, sell more iCloud storage because the “System Data” now exceeds the free iCloud data storage quota. Win-win!
The ability to walk at 40km/h speeds.
Wasn’t Google Plus used to be called Circles? Man, I feel old!
At work, if you have the option, consider using KeePassXC or similar software. That will give you a properly encrypted file with secrets and also password-manager features.
What happens if you redirect all traffic to a sinkhole, rather than to 127.0.0.1? Do the devices still freak out when they talk to a web server which returns a 404? Just morbidly curious…
Ohh, this headline aged like milk, LOL. 😂
It is powerful, as long as you don’t ask it to generate anything involving white people. 🤣😂🤣
Huh? ZFS is not 100% userspace. You’re right that ZFS doesn’t need hardware RAID (in fact, it’s incompatible), but the standard OpenZFS implementation (unless you’re referring to the experimental FUSE-based one) does use kernelspace on both FreeBSD and Linux.
The Orion browser for iOS/iPadOS supports both Firefox and Chromium extensions, however, the support is quite buggy and limited. Nonetheless, a valiant effort by Orion devs.
Noice!! 👍 Thanks for the tip!
Awww I hope she recovers.
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:
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
Legacy API and app behaviour support. Ironically replacing the registry with something more straightforward would be relatively easy, unlike adding support for storing home directories on a drive other than C. Technically you can mount a different filesystem under c:/users to achieve this, but AFAIK that’s neither supported nor trivial to do.
I tried doing it, and gave up. Sure, most software will respect the path changes in the user’s registry hive, however, every once in a while a program will just assume that your home dir lives under c:\documents and settings$username - and that’s when it all goes south. Really frustrating this lack of consistency.
All in all, the OS is riddled with hacks and “supports” for legacy runtimes and behaviours. Heck, my username is poking fun at the fact that Windows 7 had support for the 386 (yes, Intel’s 80386 processor from the late 80’s) enhanced API. Windows 7…. My username is a “tribute” to a file called krnl386.exe that implemented a bunch of legacy API calls like how much RAM a system has or whether or not the OS is running in “386 enhanced mode” that were relevant back in Windows 3.x days… and still supported in Windows 7. That pretty much sums up why Windows is, and always will be, a hot mess.
The only way to combat this is to vote the assholes out at the end of their term.
Extreme leftists are getting a little too comfortable all over the world it seems.