[Pkg-zfsonlinux-devel] Fwd: D-I && ZFS On Linux

[Aron Xu]

Hi Turbo,

Thank you for doing this really quickly, but it's not said that binary
udeb is totally impossible (here I'm not saying it's okay, either),
though Debian cannot disclose the legal analysis at this moment. So
let's hold this stuff for a moment, it's not in a hurry anyway (after
waiting for years).

Thanks,
Aron

On Sat, Apr 18, 2015 at 5:18 PM, Turbo Fredriksson <turbo at bayour.com> wrote:
> FYI: Should have Cc'd this list to.
>
> Begin forwarded message:
>
>> Resent-From: debian-boot at lists.debian.org
>> From: Turbo Fredriksson <turbo at bayour.com>
>> Subject: D-I && ZFS On Linux
>> Date: April 18, 2015 11:17:07 AM GMT+02:00
>> To: Debian Install System Team <debian-boot at lists.debian.org>
>> Cc: Asias He <asias at debian.org>
>>
>> "Some time ago" I created some patches for the debian installer to
>> provide ZoL support on Linux. Since ZoL wasn't in the Debian GNU/Linux
>> at the time, the where (of course) rejected.
>>
>> But now that we have a green light from the lawyers, I think it's
>> time to get this accepted again.
>>
>> Because the lawyers apparently said that there is no allowance
>> for binary modules (which, to me, was quite a surprise actually,
>> but lets not dwell on that - it is what it is), we talked about
>> this on #zfsonlinux a couple of days ago. The (best) suggestion
>> was to use zfs-fuse for the initial pool and filesystem creation,
>> and then build ZoL (using dkms) etc in /target.
>>
>> The ... "downside" of this is that it starts out with a v23/4 pool, but
>> at least zfs-fuse in Debian GNU/Linux supports automatic ashift detection.
>>
>>
>> For the last two days, I've been working on a prototype of this, and
>> it worked just fine. I'm currently running this through a lot of tests
>> to see if there's any hidden faults or problems.
>>
>> Had to modify 'zfs-fuse' to create an udeb, but Asias He (maintainer of
>> zfs-fuse) have taken a preliminary look at that patch, and he agrees with
>> it and said he'd apply it "when I'm ready".
>>
>> * Patch for zfs-fuse
>>  https://github.com/zfsonlinux/debian-installers/commit/3d137afe9d92ca740c3488fdbbd884f3076c5196
>>
>> * Patch for debian-installer
>>  https://github.com/zfsonlinux/debian-installers/commit/e2c23b24586d769803bd13d9b1548a4f5693cf31
>>
>> * Patch for partman-zfs
>>  https://github.com/zfsonlinux/debian-installers/commit/77002ed5774e742e510bd430d2403a7d82e576b2
>>
>> * Patch for base-installer
>>  https://github.com/zfsonlinux/debian-installers/commit/0a1ad6270a1afbaf1829834d507f5b5f17a6d313
>>
>> * Patch for grub-installer
>>  https://github.com/zfsonlinux/debian-installers/commit/e5539414ac8508ad861941b5f2ca0b98af800d59
>>
>> I'm going to need to clean these up a little (I had to do some hacks
>> to some of them to be able to distribute it for ZoL), but the question
>> is: Do I have to split up each patch into smaller chunks, or is it ok
>> with one for each project?
>
> _______________________________________________
> Pkg-zfsonlinux-devel mailing list
> Pkg-zfsonlinux-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zfsonlinux-devel