Explore >> Select a destination
|
You are here 
|
blog.cavelab.dev | ||
| | | | |
www.virtualizationhowto.com
|
|
| | | | | RAIDZ calculator to find capacity and cost data about your ZFS storage pool and compare layouts, including mirror, RAIDZ1, RAIDZ2, and RAIDZ3 | |
| | | | |
www.henryleach.com
|
|
| | | | | I wanted to create a script that would e-mail me when it detected a failure in a ZFS storage pool, but to test it I needed a failing zpool. You could create a zpool with a USB hub and some USB memory sticks, and then pull them out as you like, but that involves getting up, something I try to reserve for important things like getting a new cup of tea, or a biscuit. Luckily ZFS has the ability to create pool just from files. | |
| | | | |
www.tubsta.com
|
|
| | | | | [AI summary] The article discusses setting up a reliable bare metal server using TrueOS/FreeBSD with mirrored storage for redundancy and data protection. | |
| | | | |
nmn.gl
|
|
| | | Last Tuesday at 1 AM, I was debugging a critical production issue in my AI dev tool. As I dug through layers of functions, I suddenly realized - unlike the new generation of developers, I was grateful that I could actually understand my codebase. That's when I started thinking more about Karpathy's recent statements on vibe coding. For those who missed it, Andrej Karpathy recently shared his thoughts on what he calls "vibe coding" - essentially surrendering code comprehension to AI tools and hoping for the best. His exact words? "I 'Accept All' always, I don't read the diffs anymore." I have learnt a lot from Karpathy and use AI tools daily, but there's a world of difference between augmenting your capabilities and completely surrendering your understanding. | ||
