Re: including python in the initramfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2009-06-17 at 09:06 +0200, Seewer Philippe wrote:
> Warren Togami wrote:
> [snip]
> > This is a good case for the modules.d design of dracut.  Write your own 
> > module that does whatever you want, and install that module only in 
> > cases where you generate the initrd for your XO.  Your special module 
> > does not belong in dracut upstream.
> 
> I agree. That's what the module system is designed for among other 
> things. Have a look at README.modules and the currently available 
> modules, that should give you an idea on how to proceed.

Yes, thanks. The module system is excellent and I've already been
crafting my work as a module. Dracut is perfect in this respect.

I was just interested in the opportunity of getting some or all of our
work upstream, hence "doing it right" from the start. But I guess we're
still a bit too nutty for that. (whatever you do, don't ask about our
previous initramfs setup!)

Daniel


--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux