Title: Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi Jan:
 
You can run dd off the filesystem of the node being imaged, i.e.
 
/a/bin/dd (when it is mounted)
 
I believe dd was included in busybox/BOEL in the latest development release (3.5.3).
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Jan Groenewald
Sent: Mon 15/08/2005 07:46
To: sisuite-users@lists.sourceforge.net
Subject: Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)

Hi

On Mon, Aug 15, 2005 at 03:38:39PM +0200, Jan Groenewald wrote:
> Well, the MBR, device.map and devfs=mount now lets my nodes boot.
> Yee-haa.
Oh no. No "dd" command on the network boot image. Can I add it somehow?

> 1) They boot with a bad superblock on hda7 and hda5 (ext3 and ext2, both
> excluded from the update by localexclude). The one is /tmp and the one
> is /local (scratch space).
/dev/hda7 was never made, since it is unmounted before getimage to save
space. I put mkfs in the master script.
/dev/hda5 was a once off (weird, hey)


If I don't have dd (what is that, busybox or something which doesn't
have it?) how else can the network boot kernel and system put a file in
the MBR? I cannot chroot since then I can't see hda1, but I can mount
and access the correct MBR from the image.

Any ideas?

Jan
--
   .~.
   /V\     Jan Groenewald
  /( )\    www.aims.ac.za
  ^^-^^


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to