Hi Bjarne, I'm not sure how "easy" it'll be to switch between ZFS & EXT2/3/4/LVM for the average end user. Current method for installation of OS is simply to flash the image to disk, and you're basically ready to go--no installer like you see on x86 versions of EL. If there were an installer, I imagine it would not be too difficult to add ZFS in as an option, along with the myriad of options already available in the installer. But since there's no installer, the filesystems are already in place when you flash the OS. And I'm not aware of any way to convert in place the filesystem, at least between ZFS & EXT/LVM. That is why I made the proposal of two images, depending on what you want to use.
On Sat, May 16, 2015 at 1:10 PM, Bjarne Saltbaek <[email protected]> wrote: > Hi Mark and people. > > Freedom of choice! :) I have nothing against ZFS, I myself have been using > default choices by Redhat/CentOS in the various distributions at home and > at work meaning ext3 and ext4 with LVM. So maybe some easy wiki guidelines > on how to easy switch between the technologies and pro's and con's like the > ones you and Gordan mention. > > Like, I would love to see /var/run moved moved to a tempfs like Raspberry > suggests if you run on a SD/MicroSD. > > > BR, > Bjarne > > On 16-05-2015 18:10, Mark Campbell wrote: > >> I am also a huge fan of ZFS. I've been using it at home on my home >> server's 10TB partition for a few years now (back when that was a bit more >> impressive ;) ), and I even use it on some servers at work (big fan of the >> deduplication feature for our backup server--BackupPC + ZFS Dedup == >> Awesome). >> >> So that said, I'm highly in favor of the OPTION of ZFS on RedSleeve. As >> you've mentioned, there are some cons to it, especially to embedded devices >> with limited resources. I think these types of devices should have the >> ability to stay on ext. >> >> Plus, there's some other considerations. In my case, I am currently >> using the RedSleeve OS as a base for a product I hope one day to market. I >> chose RedSleeve because of the stability inherent in the upstream's >> derivatives, including CentOS, and last I checked, RSEL is one of a >> kind--there's just no other EL-based ARM OSes out there (which surprises >> me). So stability is very important for me. Performance too (of which >> every little bit counts on an embedded device). But another one that I >> think people often forget, is that license-wise, ZFS is not technically >> compatible with linux. There are many who choose to ignore it (myself >> included on my home server), but the fact is, if I want to bring this to a >> commercial product eventually, I'm going to have to pay attention to those >> licenses. Others in my boat will too. >> >> Perhaps a compromise--what if two images were kept? One that's more >> "vanilla", and another with ZFS? My guess is that it's a little extra >> work, but that it wouldn't be that much--you would just create the vanilla >> as usual, and branch it off to modify it with ZFS. >> >> > _______________________________________________ > users mailing list > [email protected] > http://lists.redsleeve.org/mailman/listinfo/users > -- --Mark
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
