mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Will Woods <wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] add net-lib, nfs-lib, url-lib, and img-lib
Date: Wed, 15 Feb 2012 17:56:01 +0100	[thread overview]
Message-ID: <4F3BE3A1.7000001@redhat.com> (raw)
In-Reply-To: <1329241090-26908-1-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Am 14.02.2012 18:38, schrieb Will Woods:
> Hi all,
> 
> This set of patches adds a bunch of "libraries" to dracut:
> - net-lib adds some utility functions to module 40network
> - nfs-lib provides the special nfs handling that was in 95nfs/nfsroot
> - url-lib is a new module for handling http{s}/ftp URLs with curl
> - img-lib is a new module for dealing with archives & fs images.
> 
> They might need tweaking for style/GPL headers/etc - just let me know and
> I'll fix up the patches.
> 
> Only patch 3 and 5 change existing code - the rest should be very low-risk.
> 
> Patch 3 ports the existing nfsroot to nfs-lib. This is kind of a
> proof-of-concept (look how short it is! whee!) but it *has not been tested*.
> Feel free to take or leave that patch - but if someone could apply it and
> help test it, I would be *very* thankful!
> 
> Patch 5 moves 90livenet to url-lib, and I *have* tested this to confirm that
> it works.
> 
> If these are accepted, some next steps might be:
> - move things out of dracut-lib.sh to net-lib or nfs-lib
>   (wait_for_if_up, nfs_root_to_var, ip_to_var, etc.)
> - add rpm/deb support to img-lib
>   (is there a way to do optional dependencies, specified in dracut.conf?)
> - add support for live "updates" images to livenet
> 
> Thanks for looking these over,
> 
> -w
> 

Pushed all of them and corrected nfs-lib.sh

      parent reply	other threads:[~2012-02-15 16:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 17:38 [PATCH] add net-lib, nfs-lib, url-lib, and img-lib Will Woods
     [not found] ` <1329241090-26908-1-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-14 17:38   ` [PATCH 1/9] 40network: add net-lib.sh Will Woods
     [not found]     ` <1329241090-26908-2-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-15  8:28       ` Harald Hoyer
2012-02-14 17:38   ` [PATCH 2/9] 95nfs: add nfs-lib.sh Will Woods
2012-02-14 17:38   ` [PATCH 3/9] port nfsroot to nfs-lib Will Woods
2012-02-14 17:38   ` [PATCH 4/9] add module 45url-lib Will Woods
2012-02-14 17:38   ` [PATCH 5/9] 90livenet: port to url-lib Will Woods
2012-02-14 17:38   ` [PATCH 6/9] url-lib: add support for NFS Will Woods
2012-02-14 17:38   ` [PATCH 7/9] add set_http_header to url-lib Will Woods
2012-02-14 17:38   ` [PATCH 8/9] add img-lib: a library for handling filesystem images Will Woods
2012-02-14 17:38   ` [PATCH 9/9] skiproot - script for network setup without network root Will Woods
     [not found]     ` <1329241090-26908-10-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-14 18:42       ` Will Woods
2012-02-15 16:56   ` Harald Hoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F3BE3A1.7000001@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox