nottelling @ nottelling @lemmy.world

Posts

1

Comments

111

Joined

2 yr. ago

This is an AB problem in which you're going to eventually solve the actual problem that isn't actually systemd after looking real hard at ways to replace systemd.

Or else you're going to find yourself in an increasingly painful maintenance process trying to retrofit rc scripts into constantly evolving distributions.

There's a lot I prefer about the old SysV, and I'm still not thrilled that everything is being more dependent on these large monolithic daemons. But I've yet to find a systemd problem that wasn't just me not knowing how to use systemd.

ZHA isn't compatible with a lot of recent Hue bulbs. It's a bit frustrating.

.local is reserved for mDNS responses, don't use that.

It's more than best practice. Your active directory controllers want to be the resolvers for their members, separate from other zones such as external MX records or the like. Your AD domain should always be a separate zone, aka a subdomain. "ad.example.com".

If your DCs are controlling members at the top level, you'll eventually run into problems with Internet facing services and public NS records.

Also per below. You can't get commercially signed certificates for fake domains. Self hosting certificate authorities is a massive pain in the ass. Don't try unless you have a real need, like work-related learning.

made it a subdomain

That is the correct answer.

Your experience must be extremely limited.

Conversely, as a system engineer that is involved in the hiring process for software development in addition to various types of platform and cloud engineering jobs.

I look for, in order of importance:

• demonstrated experience
• additional skills

That's it. College degree isn't even considered, but if you got relevant experience in college that can count.

Most of my interview time is spent digging into technical details to see if you can back up your resume claims. The rest is getting an idea of how you approach challenges and think about things.

As far as certifications, they're often required to get in the door due to qualification regulations. Especially security certs. If you list them, I'll ask a few questions just to make sure you actually know what's up.

Instead of paying for multiple services, I am now renting a decently sized VPS on Scaleway, and hosting all my projects on them.

That's not self hosting. That's moving your managed services down the stack from PaaS to IsaS.

It's an unserious take on the impacts as well. No discussion of availability? Backups? Server hardening and general security? Access and authentication models? Sysadmin on aVPS is more than "running a bunch of commands now and then", and the author ignores that entire workload.

I had no real idea how to phrase it, but all these posts have helped. What I was actually focused on when I posted was mainly hardware that can do what the Arlo cameras do:

• Wifi + battery/solar my house is old and hardwires are a pain in the ass.
• High def, preferably 4k, but 1080 is ok.
• Night vision, color or not doesn't matter
• Motion-activated, and preferably some way to filter out and not trigger on things like passing traffic cars.
• As small a form-factor as possible.

The Reolink hardware mentioned below seems to fit the bill hardware-wise.

I hadn't even really considered the software, as I don't need a lot of features. All I need is to use motion-activated capture to stream to some local storage, and an ability to view a live-stream when I want one. But it looks like there's a lot of options I need to consider.

Reolink looks like a solid answer, thanks.

I'm somewhat stuck on Unifi for wifi APs and Routers, because all the other consumer-grade devices can't handle the number of small IoT devices I've got. Netgear and Asus just lose connections with ESP devices and refuse to let them connect after about a dozen. The commercial grade stuff, in addition to being too expensive, is all rack mounted, high power draw and noisy af.

Aside from the fact that my stuff seems stable on the Ubiquiti hardware, I hate the products. The interface is terrible, Unifi insists on hiding the advanced networking behind a halfass gui, the SSH console lacks half the features of even that terrible gui, and every time i try to create a new routed network, the wifi devices stop connecting.

Still less than an equivalent RAID array. Particularly if you consider that archives are very rarely extracted as a complete bulk, vs pulling the specific records needed.

Guess it depends on how much you trust that Amazon is going to steal your data instead of doing the thing you're paying them for, vs a house fire or media failure or whatever.

There's also pretty clear rules about unpaid bills, the data doesn't just vaporize.

This is what we call a "risk assessment", and imo if I must have that data available long-term, then a single copy on DVDs in a closet isn't good enough.

Last months bill for my entire Amazon account was $4.72. most of that was the glacier storage.

I think you can technically do it, but it's expensive to retrieve. But that isn't the point of an archive.

OP said "archive", not "backup". Glacier is for days you need to keep but rarely touch.