summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorVictor Lowther <victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>2009-02-25 18:42:05 -0800
committerHarald Hoyer <harald@redhat.com>2009-03-04 16:54:43 +0100
commit0ac9584ded390a078a74f9026168b5f1b88d1bf6 (patch)
tree1f4271ac89c2e91501a0f4a7767fef4c69ca3ba7 /README
parent8177ca3e1e702a48c688adfac9916ebad934c8e2 (diff)
downloaddracut-0ac9584ded390a078a74f9026168b5f1b88d1bf6.tar.gz
dracut-0ac9584ded390a078a74f9026168b5f1b88d1bf6.tar.bz2
dracut-0ac9584ded390a078a74f9026168b5f1b88d1bf6.zip
We now know how to configure the network interfaces.
Provided that you are configuring them via DHCP. RARP, BOOTP, and static configuration are not written yet. Also, adding nic drivers really bloats the initrd. I am looking for feedback on these patches from people who actually implement booting over the network. This patch series does not include support for that yet -- you will not find nfsroot= handling, or booting to a fs supplied by dhcp yet. I do want to make it as easy as possible to add support for booting over the network, as well as making it easy for people to customize things to meet their site requirements. This patch series is also available as the network-configurability branch at http://git.fnordovax.org/dracut. It may be rebased without warning to keep it in sync with the rest of dracut.
Diffstat (limited to 'README')
-rw-r--r--README6
1 files changed, 5 insertions, 1 deletions
diff --git a/README b/README
index 1c377b43..6c70fc18 100644
--- a/README
+++ b/README
@@ -37,7 +37,11 @@ Some general rules for writing modules:
* Generator modules should have a two digit numeric prefix -- they run in
ascending sort order. Anything in the 90-99 range is stuff that dracut
relies on, so try not to break those hooks.
- * Generator modules and hooks must have a .sh extension.
+ * Generator modules and hooks must have a .sh extension.
+ * We have some breakpoints for debugging your hooks. If you pass 'break'
+ as a kernel parameter, the initramfs will drop to a shell just before
+ switching to a new root. You can pass 'break=hookpoint', and the initramfs
+ will break just before hooks in that hookpoint run.
Also, there is an attempt to keep things as distribution-agnostic as
possible. Every distribution has their own tool here and it's not