<story><title>BeagleV – An affordable RISC-V computer designed to run Linux</title><url>https://beaglev.seeed.cc/</url></story><parent_chain><item><author>mrweasel</author><text>Is there something inherently complicated in adding a SATA&amp;#x2F;M.2 port to board like this?&lt;p&gt;The RaspberryPi is also &amp;quot;disk-less&amp;quot;, which to me is one of the major limitations.&lt;p&gt;It&amp;#x27;s a super interesting little board, and I love that it&amp;#x27;s a RISC-V, that could really help getting the CPU in the hands of people. I just don&amp;#x27;t know enough about these things to understand why there are no storage connectors (other than an SD card slot).</text></item></parent_chain><comment><author>1vuio0pswjnm7</author><text>On the systems I can control, I do all work &amp;quot;disk-less&amp;quot;.  I strongly prefer it.  I like to keep programs and data segregated.  The basic setup on NetBSD is as follows, with endless variations possible therefrom.  The kernel(s) and userland(s), along with bootloader(s), are on external media, like an SD card or USB stick, marked read-only.  There&amp;#x27;s a RAM-disk in the kernel with a multi-call binary-based userland (custom-made using BusyBox or crunchgen).  After boot, a full userland from external media or the network is mounted on tmpfs-based or mfs-based overlay and then we chroot into the full userland.  From there, the work space is all tmpfs (RAM).^1  I can experiment to heart&amp;#x27;s content without jeopardising the ability to reboot into a clean slate.  The &amp;quot;user experience&amp;quot; is also much faster than with disk-based.  Any new &amp;quot;data&amp;quot; that is to be retained for future use across reboots is periodically saved to some USB or Ethernet connected storage media.  I do not use &amp;quot;cloud&amp;quot; for personal data.  Sorry.  This forces me to think carefully about what needs to be saved and what is just temporary.  It helps prevent the accumulation of cruft.  The number one benefit of this for me though is that I can recover from a crash instantly and without an internet connection.  No dependencies on any corporation.&lt;p&gt;This BeagleV looks like it would work well for me as it has Ethernet and USB ports.&lt;p&gt;1.  With NetBSD, I can run out of memory with no major problems.  With Linux, this has not been the case.  I have to be more careful.</text></comment>
<story><title>BeagleV – An affordable RISC-V computer designed to run Linux</title><url>https://beaglev.seeed.cc/</url></story><parent_chain><item><author>mrweasel</author><text>Is there something inherently complicated in adding a SATA&amp;#x2F;M.2 port to board like this?&lt;p&gt;The RaspberryPi is also &amp;quot;disk-less&amp;quot;, which to me is one of the major limitations.&lt;p&gt;It&amp;#x27;s a super interesting little board, and I love that it&amp;#x27;s a RISC-V, that could really help getting the CPU in the hands of people. I just don&amp;#x27;t know enough about these things to understand why there are no storage connectors (other than an SD card slot).</text></item></parent_chain><comment><author>brucehoult</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.crowdsupply.com&amp;#x2F;sifive&amp;#x2F;hifive-unmatched&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.crowdsupply.com&amp;#x2F;sifive&amp;#x2F;hifive-unmatched&lt;/a&gt;&lt;p&gt;PCIe, 16 GB DDR4, two M.2 (one for storage, one WIFI), quad core 1.5 GHz (same cores as this board, but twice as many)</text></comment>