30021190

joined 1 year ago
[–] [email protected] 19 points 10 months ago

Importantly and how it's different to FF is that it boots the content without calling the disk reset and if you keep the disk button wedged then that reset never triggers, so that copy protection isn't called, where as FF basically triggers a drive reset which is why you couldn't use that.

[–] [email protected] 1 points 11 months ago (1 children)

Looks like Three doesn't block it....

[–] [email protected] 3 points 11 months ago

Statping-ng has had some updates beyond the base.

Snorkeling is probably your best choice as it did show latency overall and not just up/down.

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago)

Write your own selinux module with audit2allow.

I'm not at work so I can't find the guides I use but this looks similar https://danwalsh.livejournal.com/24750.html

[–] [email protected] 4 points 1 year ago

Myself over NFS can have serious latency issues. Some software can't correctly file lock over NFS too which will cause write latency or just full blown errors.

iSCSI drops however can be really really bad and cause full filesystem corruption. Also backing up iSCSI volumes can be tricky. Software will likely work better and feel happy however and underlying issues may be masked until they're unfixable. (I had an iSCSI volume attached to vmware silently corrupt for months before it failed and lost the data even though all scrubs/checksums were good until the very least moment).

You can make your situations with with either technology, both are just as correct. Would get a touch more throughput on iSCSI simply down to the write confirmation being drive based and not filesystem locks / os based.

YMMV

[–] [email protected] 0 points 1 year ago

I've had issues with this too and reverted back to rooted docker. I even tried podman and system NFS mounts that it binds too with varying issues.

It looks like you can't actually do this with podman for varying reasons.

[–] [email protected] 8 points 1 year ago (3 children)

Power line adaptors

[–] [email protected] 4 points 1 year ago (5 children)

DL380 G9. Those bioses don't support booting from PCIe at all.

They actually do but it can only be a HPE supported BootROM... anything non-HPE is ignored (weirdly, some Intel and Broadcom cards PXE boot without the HPE firmware but not all).

Most of these boards have internal USB and internal SD slots which you can boot from with any media, intact HPE sell a USB SD card raid adaptor for the usb slot. So I would recommend using SD card for this...

[–] [email protected] 1 points 1 year ago

Ah no, sorry I wrongly assumed you had an DMZ/public IP.

Some routers may have automated ways to open ports but that would be highly dependent the router etc

[–] [email protected] 1 points 1 year ago (2 children)

Ports 80 and 443.

The cli is easy and you could just Cron (scheduled task) a bunch of commands to open the firewall, renew cert and close the firewall. It's how I do it for some internal systems.

[–] [email protected] 0 points 1 year ago (8 children)

I'm not sure about anything you're running but I would look into certbot.

Either using the basic web plugin or DNS plugin. Nginx would be simpler, you'd just have to open your web ports on certificate generation to pass the challenge.

I know some proxy tools have let's encrypt support, such as traefik.

view more: next ›