[Yaird-devel] Overriding some probing

[Sven Luther]

On Mon, Dec 12, 2005 at 11:20:59PM +0100, Erik van Konijnenburg wrote:
> On Mon, Dec 12, 2005 at 08:24:24PM +0100, Sven Luther wrote:
> > On Mon, Dec 12, 2005 at 07:23:22PM +0100, Jonas Smedegaard wrote:
> > > I am wondering if it would make sense to implement options to yaird
> > > making it possible to override some steps.
> > > 
> > > I want to produce a complete system in a chroot destined to run on
> > > different hardware (USB flashdisk and different mainboard) than the
> > > current machine.
> > > 
> > > I imagine yaird supporting --rootdev=/dev/sda and --rootfs=ext3 to
> > > avoid /dev/hda from the host system being ananylzed and used, and
> > > - --modules=uhci,uhci-hcd,ehci-hcd,usb-storage to add and load (in that
> > > order) the modules (and their dependands sd_mod, scsi_mod and usbcore)
> > > required for that device to show up in sysfs when booting.
> > > 
> > > If possible to "disable" probling like this, then perhaps even the
> > > problem of no upgrade path from a running 2.4-based system could be
> > > solved: A helper tool could use lsmod to produce a bloated but possibly
> > > working ramdisk image from a non-sysfs host.
> > > 
> > > Does it make any sense?
> > 
> > I think yes. What about a :
> > 
> >   --sysfs=path/to/copied/sys/tree --proc=path/to/copied/proc/tree
> 
> When debugging remotely, I've often wished for a tarball of the target
> system to be able to reproduce the issue.   A feature such as this would
> also make it possible to set up a decent test suite.
> 
> So I'm not opposed to the idea, but there's a lot of places that the
> system retrieves information from: /sys and /proc obviously, but also
> fstab, crypttab, the output of mdadm and friends.  Doing it right
> is not trivial.  Don't hold your breath for this feature unless your
> insurance has really good health coverage ...

What about a yaird tool which would assemble such a config tarball ? From all
the places where it is needed ? Then you will only have to ship a single
tarball, and just tell the user to do :

  yaird-config --get-tarball -o tarball_for_erik.tgz

Or something.

Friendly,

Sven Luther