It might already be packaged for whichever OS you’re running, and it comes with a utility to do the conversion. On Debian or Ubuntu it should be as simple as installing the pst-utils package and running something like readpst <path to .pst file> and it’ll leave an mbox file for you. It’s been a fair few years since I used it, so reading the documentation would probably be wise, but I remember it being pretty straightforward.

I don’t have a Redhat machine handy right now, but it looks like the package is called libpst there. On a Mac you’d need to follow the build instructions in the git repository, but it’s not python, the main library and utils are written in C. The tarball they refer to it just a tar of the source, that you can download form the releases page. I can’t help you if your running windows, I don’t have a machine running it, and haven’t used it in many years.

I’ve used libpst to be this in the past. On Debian it’s packaged as pst-utils. The readpst util will convert your PST to a variety of formats including MBOX.

That, or ICE kidnap him when he tries to return because he’s ‘obviously’ in league with the gang.

Before you can decide on how to do this, you’re going to have to make a few choices:

Authentication and Access

Theres two main ways to expose a git repo, HTTPS or SSH, and they both have pros and cons here:

• HTTPS A standard sort of protocol to proxy, but you’ll need to make sure you set up authentication on the proxy properly so that only only thise who should have access can get it. The git client will need to store a username and password to talk to the server or you’ll have to enter them on every request. gitweb is a CGI that provides a basic, but useful, web interface.

• SSH Simpler to set up, and authentication is a solved problem. Proxying it isn’t hard, just forward the port to any of the backend servers, which avoids decrypting on the proxy. You will want to use the same hostkey on all the servers though, or SSH will refuse to connect. Doesn’t require any special setup.

Replication

Git is a distributed version control system, so you could replicate it at that level, alternatively you could use a replicated file system, or a simple file based replication. Each has it’s own trade-offs.

• Git replication Using git pull to replicate between repositories is probably going to be your most reliable option, as it’s the job git was built for, and doesn’t rely on messing with it’s underlying files directly. The one caveat is that, if you push to different servers in quick suscession you may cause a merge confict, which would break your replication. The cleanest way to deal with that is to have the load balancer send all requests to server1 if it’s up, and only switch to the next server if all the prior ones are down. That way writes will alk be going to the same place. Then set up replication in loop, with server2 pulling from server1, server3 pulling from server2, and so on up to server1 pulling from server5. With frequent pulls changes that are commited to server1 will quickly replicate to all the other servers. This would effectively be a shared nothing solution as none of the servers are sharing resources, which would make it easier to geigraphically separate them. The load balancer could be replaced by a CNAME record in DNS, with a daemon that updates it to point to the correct server.

• Replicated filesystem Git stores its data in a fairly simple file structure, so placing that on a replicated filesystem such as GlusterFS or Ceph would mean multiple servers could use the same data. From experience, this sort of thing is great when it’s working, but can be fragile and break in unexpected ways. You don’t want to be up at 2am trying to fix a file replication issue if you can avoid it.

• File replication. This is similar to the git replication option, in that you have to be very aware of the risk of conflicts. A similar strategy would probably work, but I’m not sure it brings you any advantages.

I think my prefered solution would be to have SSH access to the git servers and to set up pull based replication on a fairly fast schedule (where fast is relative to how frequently you push changes). You mention having a VPS as obe of the servers, so you might want to push changes to that rather than have be able to connect to your internal network.

A useful property of git is that, if the server is missing changesets you can just push them again. So if a server goes down before your last push gets replicated, you can just push again once the system has switched to the new server. Once the first server comes back online it’ll naturally get any changesets it’s missing and effectively ‘heal’.

We didn’t steal the balls, but where computers were back to back we’d swap the mice over. Cue much confusion for the next class when the pointer seemed to move on it’s own. Fun times.

It’s not exactly what you’re talking about, but it looks like there is a way to do this over PCIe 5.0: CXL 1.1. The m.2 bus exposes up to 4 PCIe lanes, so it may be possible, with the right combination of motherboard that supports CXL, and a CXL module with an m.2 interface, to do what you want. I haven’t dug much deeper than that, but maybe it’ll be of some help.

Oh, well done.

Whilst I appreciate the source material, in this case it’s not even danger he’s running away from, it’s being rubbish at a game he claimed to be good at.

I manage all my homelab infra stuff via ansible and run services via kubenetes. All the ansible playbooks are in git, so I can roll back if I screw something up, and I test it on a sacrificial VM first when I can. Running services in kubenetes means I can spin up new instances and test them before putting them live.

Working like that makes it all a lot more relaxing as I can be confident in my changes, and back them out if I still get it wrong.

Seriously. Can you imagine, you’ve had this process running quietly for years, and it’s getting you round some awkward tax or import restriction somewhere, you’re making a tidy extra profit, and you don’t even feel too bad about fidfling the paperwork a bit, after all, who’s going to notice, a bunch of flightless birds? Then along comes the orange idiot and his cadre of fascists and accidentally expose you because they don’t understand how to rationally calculate tarrifs and just get an intern to copy and paste from the nearest LLM.

It’s laughing at this sort of thing that’s jeeping me sane right now.

It’s got to be something like that, there was something like $1.3m of machinery exports from an island populated by penguins. Someone was doing something naughty, and whilst the way these tarrifs are calculated is idiotic, it’s fun that it’s exposed sonething like this.

Canaries were taken into coal mines to warn the miners of poisionous gasses by dropping dead. When the canary metaphorically picks the lock on its metaphorical cage and literally makes a break for the border, I think you can consider that a sign of a similar magnitude.

That’s just crazy talk. If we don’t listen to the billionaires the line might not keep going up quite so fast. For the purposes of this argument, please ignore TSLA, the climatologists obviously got to that one.

As @Tahl_eN@lemmy.world said in another comment, there’s concentration and there’s flow (aka the zone).

Concentrating takes effort, is often tiring, and requires disipline to block out distractions. It can feel good to consentrate on a problem or task, give it all your mental energy, and achieve your goal. It can be a fragile state though. If a distraction does break through it can completely disrupt your thought processes, causing you to lose track of everything you had in mind, and effectively sending you back to square one. Practice helps avoid that, but concentration is inherently mentally taxing.

Flow is different. You will probably only reach it through concentration, and may not jnitally be aware of the transition, but you’ll know it afterwards. The complex becomes simple, stuctures untangle themselves at a thought, you feel mental clarity unlike any other time, everything you’d been struggling with becomes effortless, and time ceases to have any importance. It’s more like a trance or meditation than a normal mental state, and you can stay in that state until your body physically runs out of energy. I’ve ended up sitting at my desk for nearly 24 hours without rising, and without eating or drinking, utterly engrosed in the task at hand, not noticing the sun setting and rising again, and felt entirely calm and rested at the end of it.

That’s would appear to be the plan, yes. Push people to riot, declare marshal law, turn it into a full blown civil war and rely on the assumption that right wingnuts are more likely to be armed than those who oppose fascism. I fervently hope it does not come to that, and some way is found to stop it in time, but the future currently looks rather bleak in that respect.

Ah, ok. You’ll want to specify two allowedip ranges on the clients, 192.168.178.0/24 for your network, and 10.0.0.0/24 for the other clients. Then your going to need to add a couple of routes:

• On the phone, a route to 192.168.178.0/24 via the wireguard address of your home server
• On your home network router, a route to 10.0.0.0/24 via the local address of the machine that is connected to the wireguard vpn. (Unless it’s your router/gateway that is connected)

You’ll also need to ensure IP forwarding is enabled on both the VPS and your home machine.

The allowed IP ranges on the server indicate what private addresses the clients can use, so you should have a separate one for each client. They can be /32 addresses as each client only needs one address and, I’m assuming, doesn’t route traffic for anything else.

The allowed IP range on each client indicates what private address the server can use, but as the server is also routing traffic for other machines (the other client for example) it should cover those too.

Apologies that this isn’t better formatted, but I’m away from my machine. For example, on your setup you might use:

On home server: AllowedIPs 192.168.178.0/24 Address 192.168.178.2

On phone: AllowedIPs 192.168.178.0/24 Address 192.168.178.3

On VPS: Address 192.168.178.1 Home server peer: AllowedIPs 192.168.178.2/32

Phone peer: AllowedIPs 192.168.178.3/32