I'm going to say, yes. Add an mtools dep. It is what my suse systems
use, and if memory serves, it's what redhat packages it as too.


However, I believe it's the client package that really uses this.  This
is how we tell what kind of FAT a client has, so that we can re-create
it properly.


Thus spake Dann Frazier ([EMAIL PROTECTED]):
On Thu, Mar 11, 2004 at 06:16:42AM -0500, Mark Seger wrote:
which you can see I got just before rsync started copying the image. is this going to prevent the image from being correctly copied or is it more of a warning?

You should install the package that provides minfo - in fact, it should be added as a dependency of the rpms. In debian, the mtools package provides minfo, and systemimager-server depends on it.

Jerry - should I add an mtools dep to the spec file?  is that the package name on rpm
based systems?


------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users


--
---------------------------------------------------------
Brian Elliott Finley Argonne, MCS Division Phone: 630.631.6621 http://thefinleys.com
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
---------------------------------------------------------



------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to