[Nix-dev] [PATCHES] vsftpd and filesystems

Bryce L Nordgren bnordgren at gmail.com
Sat Feb 25 20:33:33 CET 2012


On Sat, Feb 25, 2012 at 12:45 AM, Mathijs Kwik <mathijs at bluescreen303.nl>wrote:

> On Fri, Feb 24, 2012 at 5:41 PM, Bryce L Nordgren <bnordgren at gmail.com>
> wrote:
> >
> >
> > Tried that. No go. Correct me if I'm wrong, but I think initrd is
> "stage1"
> > and filesystems.nix, as an upstart job, runs after the stage2 kernel is
> up
> > and more or less stable. Maybe we need a boot.stage2.kernelModules?
>
> You are right, but it shouldn't matter. If you load modules in initrd,
> they stay available for the full run of the system.

Anyway. There's also boot.kernelModules. Those get loaded in stage2
> and aren't included in the initrd. In your case, where your root fs
> isn't on btrfs, including the module there should still be fine.
>




> I attached a patch that does just that.
> So if you take care of loading the module in any of the 2 stages
> (boot.kernelModules should be fine in your case (non-root)), this
> should have the same effect as your patch.
>
> Can you give it a try and report back here (don't forget to cc nix-dev)?
>

I'll try your patch with both, but I know that putting btrfs in
boot.initrd.kernelModules still requires the modprobe line before the
device scan line. I have to wait till I get into the office to try it out,
tho.

Boy, scanning thru a list of attributesets to see if any of them contain
btrfs sure looks easy (now). :)

Thanks for your help!
Bryce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20120225/e299c259/attachment.html 


More information about the nix-dev mailing list