“smb big sur”

I had been using @available( macOS 11.0, * ) to test for Big Sur, but as of the Xcode 12 GM, that doesn't seem to work any more. Whereas @available( macOS 10.16, * ) does work. Is that the right thing to use, or is it a bug?

I am working on an emulator for some legacy hardware. I recently changed the emulator to use the vmnet framework for network access rather than the old Berkley packet filter (/dev/bpf) device. It works just fine in macOS Catalina. In Big Sur beta 6, the vmnet_start_interface completion handler is never invoked unless the call to start the interface failed. I've submitted FB8648370 to report this. Here's some sample code that demonstrates the problem. Compile it with -framework vmnet and run it with privileges via sudo. On Big Sur, it will timeout after 1 minute. vmnet.c - https://developer.apple.com/forums/content/attachment/f4a79dd9-f801-4171-b1d0-d62fdad38df0

I've got a WD My Passport 1TB SSD external drive. I also have 2 MacBook Airs, one mid 2013 and one less than a month old. I used the hard drive to transition from the old one to the new one. Both worked great. I had the old one enrolled in the beta program so of course after moving to the new one it was too. They both upgraded to Big Sur one night. Long story short one of the programs I use regularly wasn't ready for Big Sur so I attempted to go back to Catalina. I plugged in the hard drive and it just sat there steadily flashing the light. No access in Finder. I opened DiskUtility and there it was, greyed out with no access.. No mount, no first aid, nothing. So I opened Safari and did some looking. Meanwhile, I cleared out the old MacBook and loaded a new version of Catalina. Turns out, when I force quit fsckhfs, the drive is accessible and I can access it. While it passes all tests on WD's utility app, when I try to run first aid it fails after about 4 hours. Though I can

I'm trying to debug a kernel extension on Big Sur (xnu-7195.0.0.141.5). In the past, I've successfully used kdp-remote from lldb to attach to the crashed kernel and debug it. However, this doesn't seem to be working on Big Sur. The serial console of the crashed machine shows: ethernet MAC address: 00:0c:29:43:dd:b5 ip address: 192.168.1.250 Waiting for remote debugger connection. as expected, but there's no response to packets sent to that address by lldb. Is this working for anyone else? Thanks, Simon

When trying to connect to another Mac running Big Sur (beta 5) using file sharing (smb or afp), it won't accept the username/password. The dialog just shakes and won't connect. I could connect from a Mac running Bug Sur to another Mac running Catalina fine but not the other way around. Anyone got a workaround? Reported as FB8520247

After migration from Catalina to Big Sur 11.1 I noticed that an Automator PrintPlugin does not work anymore. It is rather simple and consists of a single action: NewMailMessage. Mac Analytics Data - https://developer.apple.com/forums/content/attachment/5fb4f6a8-e83f-42c6-be5c-84bf1a7501b9 Running the same action from an Automator quickaction on files works as expected: Mail gets generated with selected files attached. regards Hans-Peter

After updating to big sur I've noticed that there are some cases where ui elements get automatically selected (focused?) in my MacCatalyst app. This is problematic for me in a couple of cases where there is app logic that gets triggered when a textview is initially selected and calls didBeginEditing. The two areas where it seems prevalent are: dismissing modal views and reloading tables. I've poked around into the focus engine and tried to extend textviews to not be focusable to no avail. Anyone else seeing this problem?

After installing Big Sur Beta 1, a Time Machine dialog popped up that I thought I ignored. Later I see that it backed up my iMac onto a volume called TimeMachine Backup (which is not the name of my main TM Backup so I felt this was fine). Today I actually started to look at what was happening. Big Sur renamed my TM Volume from the previous name to this TimeMachine Backup and has intermingled it's backup files with my previous Catalina ones. Quick note about my setup. I'm running Catalina on a stock SSD in the iMac. I have a USB enclosure with 4 HDs in it. One of the 4 drives is dedicated to TM Backups. I partitioned that drive to install Big Sur onto. So I run Big Sur from a 100GB Partition on this 4TB drive. Is there any way to: Break this intermingling or do I just erase the backup and have it start again from Catalina? Is TM smart enough to know which files belong to which backup OS? I booted into Catalina today and see that it thinks

Hi, I recently updated to the Big Sur beta and noticed the control center isn't in the top right corner like in the demos, pictures, etc. Instead there is a spotlight icon that won't go away even when I turn it off in the menu bar settings. Is anyone else getting this error and if so has anyone resolved it? I understand this is a beta, but this doesn't seem to be an error that is prevalent in the other systems that upgraded. Thanks.

Hello- my MacBook did the Big Sur update this evening and now it has reset my settings to where I cannot print my shipping labels from pirate ship. All of the settings have changed and when I go to print it gives me a printing error. It’s only giving me a US letter size to choose from and he used to give me different options and the one I need is no longer there. Please help where is this is affecting my business to ship out my packages to customers. Thank you! Gary K

I have Big Sure Dev Beta 1 installed on an external USB-C SSD drive. Mac is a brand new 2018 Mac mini (most recent Intel model). Beta 1 works fine (well, for the purpose of beta testing anyway Big Sur Dev Beta #2 is out now. Software Update GUI Pane and CLI both see the new update, but I'm unable to downed/install it. Here is the error I see from running 'softwareupdate -d -a' from Terminal: 'Failed to download & prepare update: Error Domain=SUMacControllerError Code=7722 [SUMacControllerErrorPreflightPrerequisiteCheckFailed=7722] Failed to perform PreflightPrerequisite operation: com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6) | The volume can not be used because it is not snapshot booted.'

The system call ntp_adjtime sets and returns various attributes associated with the NTP phase locked loop in the Darwin kernel via a struct timex argument. The frequency of the the loop is passed back and forward in this struct as a signed fractional number. In Big Sur, instead of returning a negative number for the frequency when required, ntp_adjtime returns the unsigned representation of the number - i.e. the value is always positive and can be 'off' by 65536. I have submitted FB8561779, along with a simple test case demonstrating the problem. I hope it will be fixed soon.

I am trying to install big sur on my brand new 2020 Mac Book Pro with 64gb of ram. But is keeps freezing at 12 minutes. I've let it run for 20 minutes and its still at 12 minutes. Any ideas would be more than welcome

I have now installed Big Sur 11.2.3 but I have a problem with the new Apple system lock that is safe to read-only system file and fonts inside the system folder I need any way to help delete some fonts in the system can anyone help thank you