From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
Date: Tue, 22 Feb 2005 21:48:35 +0000 [thread overview]
Message-ID: <20050222224835.C2736@banaan.localdomain> (raw)
In-Reply-To: <20050217210620.A20645@banaan.localdomain>
On Tue, Feb 22, 2005 at 06:48:29PM +0100, Harald Hoyer wrote:
> Erik van Konijnenburg wrote:
> > - More serious may be the use of PROGRAM="..." in udev.rules; this again
> > sucks in executables and shell scripts that make it difficult to find
> > out what should go on the image. It may be possible to write a
> > separate rules file for use on initrd that avoids the PROGRAM="...";
> > it would help to make the rule format richer, so that more cases can
> > be handled without resorting to PROGRAM="...".
> >
>
> Another problem arises, if you edit one config file for the udev/hotplug/init
> process, all kernels initrd have to be recreated, unless we have a hotplug
> replay mechanism after root is mounted. Though any modprobe.conf scripts which
> are not in initrd, will not be executed.
That, plus I want a back-out option ...
It seems the image depends on a combination of kernel, modprobe.conf
(for module options) and the hotplug config files; almost like we need
a makefile to do the mkinitrd invocation. This is really too complicated
for me to think about now, but it's something to consider if we want
to offer the sysadm a robust environment.
Regards,
Erik
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-02-22 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 20:06 [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts Erik van Konijnenburg
2005-02-17 21:50 ` Jeff Garzik
2005-02-17 22:50 ` Roman Kagan
2005-02-19 2:00 ` Erik van Konijnenburg
2005-02-22 11:51 ` Roman Kagan
2005-02-22 17:48 ` Harald Hoyer
2005-02-22 19:26 ` Patrick Mansfield
2005-02-22 20:03 ` Roman Kagan
2005-02-22 21:25 ` Erik van Konijnenburg
2005-02-22 21:48 ` Erik van Konijnenburg [this message]
2005-02-22 22:57 ` Erik van Konijnenburg
2005-03-17 8:26 ` Werner Almesberger
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=20050222224835.C2736@banaan.localdomain \
--to=ekonijn@xs4all.nl \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).