Yeah, if this is what it takes to get new design nuclear facilities in the US, then I’m counting it a win, but I won’t count it either way until the watts come out. Who knows: if they run ok, an actual power company might even try one.
And X-windows. There’s a few server tasks that I just find easier with gui, and they feel kind of laggy over 1G. Not to mention an old Windows program running in WINE over Xwin. All kind of things you can do, internally, to eat up bandwidth.
You’d need some way to cache that video, though, because it’d take 24 hours to write 8TB at SD card speeds of 80 MB/s.
I have isc-bind running behind pihole so network clients can register their own hostnames, and as near as I can tell, that’s outside the scope of pihole’s DHCP and dnsmasq. Pihole alone is probably fine if you only want to name static hosts, but (I understand) Unbound doesn’t support ddns, either.
pihole, in front of my own DNS, because it’s easier to have them to domain filtering.
mythtv/kodi, because I’d rather buy DVDs than stream; rather stream than pirate; but still like to watch the local news.
LAMP stack, because I like watching some local sensor data, including fitness equipment, and it’s a convenient place to keep recipes and links to things I buy regularly but rarely (like furnace filters).
Homeassistant, because they already have interfaces to some sensors that I didn’t want to sort out, and it’s useful to have some lights on timers.
I also host, internally, a fake version of quicken.com, because it lets me update stock quotes in Quicken2012 and has saved me having to upgrade or learn a new platform.
If you email to people on gmail or outlook, won’t Google and Microsoft still end up with copies of most of your mail?
Ditto on hardware raid. Adding a hardware controller just inserts a potentially catastrophic point of failure. With software raid and raid-likes, you can probably recover/rebuild, and it’s not like the overhead is the big burden it was back in the 90s.
Once you have a microcontroller running things, adding new features is just a matter of software. Doesn’t add to the BOM, doesn’t complication production in any way. There’s almost no marginal cost to techify everything, and the people who don’t want those features can just not use them. The small minority of people who want a repairable car that they can understand and maintain in their own garage are undesirable customers who reduce after-market revenue.
In the US, plug-in hybrid is a decent way to cover the breadth of consumer desires. Get a battery big enough for 50 miles of daily commuting, but have the ICE for 500 mile holiday trips. More complicated, having both power systems, and you still have the tie to gasoline, but you don’t have to lug a massively oversized battery pack everywhere you go and you still get most of your transportation energy from the electric grid.
It’s even easier with digital broadcast. I finally had to give up my PCI tuner, because who puts PCI slots on a modern mobo? $25 will get you a USB TV tuner capable of getting all the OTA and cable channels. I used to get, like, 7 analog OTA channels - ABC, CBS, NBC, PBS, and a regional independent - but I get 30 digital. All the majors have added 3-5 channels of SD reruns or other filler. I mean, it’s mostly shit, and the only thing I actually watch is local news, but for a one-time $25 cost, it’s a great supplement to streaming.
My biggest problem with MythTV is it doesn’t interface with streaming, so I use Kodi on the frontend to source from mythtv, netflix, hbo, or whatever.
I just don’t like my logs filling up with scripted login attempts. Even with fail2ban, for a while there I was getting 100+ login attempts every day, and it upset my sense of order.
This is an old post about ipv6, but it inspired me to go looking, and I wanted to share my findings.
for globally routeable IPv6 addresses, probably do let it happen automatically, either direct from the ISP, through the router by prefix delegation, or your own implementation of prefix delegation.
for devices you want to access, internally, create a ULA within the fd00::/8 space, and assign numbers (and names) however you like. Translate all your 192.168.x.y IPv4 addresses to fd00::x:y and go. Only limitation is you won’t be able to access those devices, using the ULA, from outside your network.
you can do both of these on the same subnet, and devices pick up both addresses then use the global address for internet and the ULA for intranet.
That means you can do dhcp, dynamic DNS, private domains, and all the stuff you know about IPv4 for IPv6, and still do all the stateless autoconfig that “they” want. Some devices, like my android phone, never played well with dhcpd6, but immediately preferred IPv6 as soon as I let them SLAAC.
If the prefix assigned by the ISP doesn’t change, then device SLAAC address shouldn’t change, either, because they’re calculated from MAC, so if you need to access some internal devices from the internet, you have to mark that address, but (IMO) marking the full address is not that much worse than marking the prefix and remembering the device number.
I do ssh because I’m more comfortable with it: it’s ubiquitous and as close to bulletproof as any security. Put it on a nonstandard port, restrict authentication to public keys, and I have no qualms.
Heh. House I rented was built before ubiquitous electricity. At some point, someone slapped a fuse box on the outside of the back wall and drilled a bunch of 1" holes in said wall to pass wiring. House was built on piers, so they just dragged wires around to places where they wanted outlets, which were mostly planted in the floor. Not a ground wire on site. I have no idea how they got away with renting that out, but it’s not like I called code enforcement, either.
Yeah, I think it really depends on use case. Like, I’m trying to imagine what aspect of my home lab could go so wrong, while I’m out of the house, that it would need fixed right away, and there’s nothing. I only leave my house for work or maybe a week of vacation, though, and I can imagine someone who’s occasionally away from home/house for 6-month deployments, or has a vacation home they only visit four weekends a year, might want more extensive remote maintenance. I’d still want to do that via ssh or vpn, but that’s me.
Yeah, my ISP “supports” IPv6, but assigns a /128 to users. It seems to wipe out most of the desirable features of IPv6, and has probably given me a distorted view of its philosophy. OTOH, it did force me to learn how to do DNS views, so names can have the ULA address inside and the global address outside the house, which is pretty cool.
IPv6 does have private spaces. Any prefix beginning with fd is ‘private,’ and (IIRC) there’s a formula to generate the next 40 bits of prefix to minimize the chance of intersections. i.e., you can generate your own internal /48 functionally equivalent to 192.168/16 or 10/8
Don’t know if you can use that with SLAAAC, but it works if you run a dhcpv6 and makes ipv6 feel a lot like ipv4. You have to NAT everything inside &c, but if you already have a functioning internal IPv4 network, IPv6 is just a matter of figuring out which config options need to be changed (eg, dhcp6.name-servers for option domain-name-servers)
Definitely agree for a single install. If OP has a bunch of these installs to do, then editing an install USB to configure networking and enable sshd might be worth the effort. Do the install over ssh and hope the machine starts up as desired, but even then, if it doesn’t just magically appear on the network, he’s going to need a monitor to see where the startup failed.
Raspberry Pi’s disk imager will let you pre-configure networking, accounts, and ssh, so you just write the image to an SD card, plug it in, and go. That’s a great solutions for systems usually meant to be headless and removable media. If OP’s client hardware allows, he could plug in the M2 or SATA drive meant to be the server’s startup, install Deb there, and. transfer to the server hardware. That’s definitely more work that just swapping the keyboard & monitor, but it accomplishes OP’s stated goal. (Otherwise, a lot of this thread follows the linux meme of “How do I [X]?” “[X] is dumb, do [Y] instead.”)
I don’t so much care where it’s made. The real selling point, to me, for Pi is that their products are well documented, in English, and solutions for problems are easily googled. There’s tons of SBCs out there, some of them even inexpensive, but I can’t tell if any are going to last longer than a single production run. Meanwhile, I can still buy a Pi 3 after almost a decade. Or I can take the hat I made for a Pi3, plug it straight into a new Pi Zero, and expect it to work without changes.
IPO is a big step down the path to enshittification, especially when there’s no clear, dominant alternative.
RAID is more likely to fail than a single disk. You have the chance of single-disk failure, multiplied by the number of disks, plus the chance of controller failure.
RAID 1 and RAID 5 protect against that by sharing data across multiple disks, so you can re-create a failed drive, but failure of the controller may be unrecoverable, depending on availability of new, exact-same controller. With failure of 1 disk in RAID 1, you should be able to use the array ‘degraded,’ as long as your controller still works. Depending on how the controller works, that disk may or may not be recognizable to another system without the controller.
RAID 1 disks are not just 2 copies of normal disks. Example: I use software RAID 1, and if I take one of the drives to another system, that system recognizes it as a RAID disk and creates a single-disk, degraded RAID array with it. I can mount the array, but if I try to mount the single disk directly, I get filesystem errors.