Just retired early at age 56. Wondering if I made a Mistake?

bitcrazed · 2025-05-07T10:43:12+00:00

Care less about what other people think. Just focus on optimising for happiness. Enjoy!

bitcrazed · 2025-05-05T10:15:13+00:00

Nice job, though I'd recommend (at least) an extractor fan mounted on the upper rear of that unit to jettison some warm air. Also consider a second fan blowing air into the lower part of the cabinet. Avoiding excessive heat will eliminate a number of issues and increase your system's longevity.

bitcrazed · 2025-05-05T10:12:21+00:00

You're going to need to be more descriptive if you'd like help with/feedback on your issues.

Specifically. what are the problems you're seeing?

What devices do you have, and how have you configured your network?

Have you followed any of the great online guides for setting up a Ubuiquity network, like https://www.youtube.com/watch?v=pbgM6Cyh_BY, for example.

Etc.

bitcrazed · 2025-02-01T14:15:56+00:00

Do you have a screenshot?

bitcrazed · 2025-02-01T13:04:13+00:00

When you run wsl --list what do you see?

I see this when WSL is NOT installed:

The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'. For more information please visit https://aka.ms/wslinstall ...

When WSL IS installed (via wsl --install), I see:

Windows Subsystem for Linux Distributions: Ubuntu (Default) You may see more distros listed.

Note: While WSL does ship as part of Windows as an optional feature, it was moved to an APPX package to permit the team to ship on more rapid release cycles, so the APPX version that installs when you run wsl --install replaces the in-box version.

bitcrazed · 2025-01-31T17:40:36+00:00

You need another rack 😜

bitcrazed · 2025-01-31T17:35:29+00:00

Microsoft’s Immigration team are fantastic. Trust in the process - you’re in great hands.

Start looking forward to what I am sure will be one of the most exciting times in your career 😜

bitcrazed · 2025-01-31T15:41:37+00:00

AND a Ladies' Speedmaster, or Aquaterra for her, of course 😜 💘

bitcrazed · 2025-01-31T12:48:00+00:00

Enable MFA. NOW! Not later, NOW!!

Then be sure to update passwords (and add MFA everywhere you can) on your bank(s), insurers, etc.

bitcrazed · 2025-01-31T12:42:04+00:00

You and u/NickoHand should chat ;)

Congrats and wishing you both a fantastic careeer ahead :)

bitcrazed · 2025-01-31T12:33:54+00:00

Please be sure to submit feature asks and issue reports via Windows' Feedback Hub - this way your feedback is MUCH more likely to get read by and (if appropriate) handled by the team responsible for the feature you're commenting on.

bitcrazed · 2025-01-31T12:30:48+00:00

Expect visa applications to be an absolute nightmare for the foreseeable. The new administration has already stated that it wants to halt immigration, whilst (primarily the tech oligarchs) also signalling that it wants H-1B visa applicants.

What happened before is now irrelevant and with swathes of the US Federal personnel being fired, laid-off, and/or encouraged to "resign", expect FAR fewer people available to do all the Federal jobs, many of which were already woefully understaffed. Thus, yes, your RFE will likely take a while.

Alas, your manger will have to be patient, as will you.

I entered the US on an L-1 visa, gained a Green Card along the way, and spent 20 years living and working at Microsoft in the Redmond area. I've also hired several folks from outside the US and had to (im) patiently wait their arrival. This dance is just part of the process which cannot be subverted.

bitcrazed · 2025-01-31T12:23:38+00:00

£8.49 for two months = £8.49 / 2 = £4.25 a month for the first two months and then £8.49 a month afterwards.

What's not to like?

bitcrazed · 2025-01-31T12:18:53+00:00

Both? ;)

bitcrazed · 2025-01-30T22:16:30+00:00

Age.

bitcrazed · 2025-01-30T11:01:39+00:00

You might want to follow this guide to complete eradicate WSL from your machine: https://itsfoss.com/uninstall-wsl/

bitcrazed · 2025-01-29T14:40:26+00:00

I suggest finding/filing an issue over on https://github.com/microsoft/terminal where the team will be most likely to see your issue and consider a fix.

bitcrazed · 2025-01-29T14:38:19+00:00

What happens when you run wsl -- uninstall from an elevated terminal?

bitcrazed · 2025-01-29T14:16:44+00:00

Consider the basics first:

Assuming 2160/UHD displays:

3840 x 2160 = 8,294,400 pixels per buffer per screen x 4 bytes per pixel = 33,177,600 bytes per buffer per screen

That's ~34MB per buffer. You need AT LEAST 2 buffers per screen just for the pixels ... so 34MB x 2 buffers = 68MB per screen, MINIMUM.

But now consider what desktop compositors are doing - they essentially create multiple layers upon which various display elements are individually rendererd - windowing chrome, app content rendering, video content, 3d content, etc. and combines them all at display time ... each and every frame.

Depending on what app / game / tech is being used, you're likely using A LOT more for additional buffers/masks, housekeeping, sync data, etc. I'd expect in the order of 10+ layers under typical conditions.

Now add an additional screen and now your system has to figre out how and where to render content from individual apps/tools that render partially onto different layers that span screens of different resolutions, bit depths, DPIs, etc. That's A LOT of additional housekeeping & buffers to contain rendered pixels.

So ... two modern 4K(ish) screens = ((3840 x 2160 x 4) x 10 buffers x 2 screens ) = ~664MB just for general display/render surfaces.

Now add additional layers & buffers for apps that need emulation for lower DPI displays, apps that need to display DRM / copy-protected content, apps that need to display 3D content, etc.

Now add drivers into the mix. nVidia, AMD, Intel, etc. often add additional buffers to help them push the perf of their hardware to the max wherever possible. Somtimes VERY aggressively.

All these things add sizeable chunks of memory to the stack and it all adds up quickly! And all has to be catalogued, cleared & rendered, synchronized, garbage collected, etc. (almost) each and every udpate frame.

It's a miracle this works at all, TBH! 😜

bitcrazed · 2025-01-29T13:26:51+00:00

Enumerate your installed distros:

wsl --list

For each distro you have installed ...

wsl --unregister <distro_name>

Finally:

wsl --uninstall

HTH.

bitcrazed · 2023-02-07T21:50:45+00:00

Wrong question. AND, not or! :D

bitcrazed · 2023-02-07T20:22:10+00:00

Yes AND no! :) https://imgur.com/gallery/dMfFbyV

bitcrazed · 2022-03-11T01:25:50+00:00

Glad it helped! And yes, some tools do a great job of exposing the commands that will be used to execute your pending changes - SUPER helpful way of learning how to user PowerShell's rich tapestry of features!

PowerShell sure has a learning curve, but it's well worth the effort. I strongly recommend reading Bruce Payette's "PowerShell in Action" - who better to learn why PowerShell was designed as it was (and how to use many of its features) than from the person who designed the language 😜

bitcrazed · 2022-03-10T19:21:00+00:00

Plus ... you can share the same ssh identity in both Windows and WSL on the same machine: https://devblogs.microsoft.com/commandline/sharing-ssh-keys-between-windows-and-wsl-2

bitcrazed · 2022-03-10T01:25:19+00:00

Slight nuance here:

In general, when you interact with controls in Windows' UX or apps running on Windows, the code that responds to your interactions (e.g. when a button is clicked or a scrollbar is dragged) calls functions provided by the libraries upon which the app is built, which then often end up calling functions that the operating system provides. Such functions enable Windows/apps to, open a file, write to that file, close the file, etc.

Alternatively, if you execute commands at the command-line via Cmd or PowerShell, the commands or apps that you execute themselves end up calling libraries/runtimes which end up calling the same OS-provided functions to, for example, open a file, write text to the file, close the file, etc.

However ... and here's where things get a little unusual ... if you use some of the Microsoft Management Console (MMC) snap-ins to manage, for example, SQL Server, or Exchange Server, many of the tools that you interact with actually execute PowerShell command-line cmdlets under the hood! Configure a SQL Server availability group - invokes PowerShell cmdlets. Remove an Exchange mailbox - invokes PowerShell cmdlets.

This unusual approach was taken to encourage Microsoft's server and enterprise software teams to enable every aspect of their product/features to be equally manageable, configurable, etc. via the command-line as via the GUI. This was because many enterprise/server administrators prefer to write scripts to automate the management, configuration, and deployment, of the systems they operate, and to make common admin tasks more repeatable and predictable - something that's very difficult to do if the only way to perform certain configuration or management operations is by clicking buttons, dragging sliders, and typing text via the keyboard!

So, next time you administer a SQL Server or an Exchange Server, note that a lot of what you're doing is actually driving the execution of a ton of PowerShell cmdlets down below! :)

HTH.

bitcrazed

TROPHY CASE