Customizing a base distro sounds like a good place to start 👍🏽
pyr0ball
joined 2 years ago
Hijacking for my own idea: what if I wanted to make my own updated version of say, hiren's Linux environment that included tools for data recovery and drive administration among other things. I would love to basically build my own custom recovery environment preloaded with all my favorite tools.
Tbf, with a few hours of googling, I could probably figure this out for myself so don't go through a bunch of trouble unless you want to document for others. I'm mainly posting because I saw OP and wondered if something easy already existed?
The dad jokes are strong with this one
Think you might be a little lost my friend....
I could learn a lot from you
Lol so he put even less effort into it than we thought
👏⏱️👏
Let us know how it goes!
The stepper drivers run directly of the main power supply through Vcc, so assuming you haven't added any extra heaters or other crazy amounts of power draw, you should be just fine adding another motor.
Using the second z for stability would be a more traditional use of those parts but your idea sounds like a lot of fun!
You can't both bridge your current router and use it for WiFi AP because of the hierarchy of the network. You'll need either a compatible AP-capable WiFi radio in your be router (hard to find, limited compatibility, I think you might top out at WiFi 4e (ac1350) in terms of what hardware is available.
Alternatively, you can use a dedicated access point alongside your new router which is easier and will get you better, more up to date, technology
Get yourself a decent router capable of running OpenWRT, which will allow you to set up vlan's for your lab, and (I would also recommend) another separate vlan for your IoT and other "smart" devices.
The TP-Link Archer C7 is old but reliable and has a lot of open source support.
If you're feeling more adventurous You could also build your own router with any computer that's got two or more Ethernet ports using PFSense, Firewall-NG, or IPFire
This sounds like a perfectly workable solution!
I assume getting a persistent environment in a USB recovery stick is a bigger task? I'm imagining that, with your method, I would need to repeat this process any time I wanted to update the image or load specific new kernel modules/drivers?