Title: Re: [Sisuite-users] using a loop mounted .img file as the client image

That makes sense.
What I'm actually trying to do is just make an image of the / partition
(writing to a different partition).  I'll have to mount the partition
image and copy the contents of /opt and /var into it.  I'm thinking that
should work pretty well as the base for a sis image.

John Jolet wrote:

>the problem with putting it on the drive is as it builds the file, sooner or
>later, it hits the file itself...now you're in an endless loop.  tar has the
>same issue.
>On Thursday 10 November 2005 08:46, Daniel Crandall wrote:

>
>>Ah I didn't know about not being able to put the file on the hard drive
>>that is the source.  I'm not intending to do that, but I had made an
>>image of a node system , was trying to test the image file while it was
>>still on the node.  That was not working, and now I know why.  Thanks!
>>
>>I wonder if I can use a file system utility to shrink the image file
>>down to the size of just he data?
>>
>>John Jolet wrote:
>>   
>>
>>>On Wednesday 09 November 2005 10:02, Daniel Crandall wrote:
>>>     
>>>
>>>>Hi,
>>>>
>>>>Due to the fact that OSCAR uses a version of SIS in which si_getimage
>>>>does not work properly, I'm looking at other ways to generate an image
>>>>       
>>>>
>>>>from a golden client.
>>>     
>>>
>>>>I had an idea to used dd to create a .img file from the system disk on
>>>>my golden client, then move that image to my image server and loop mount
>>>>it on /var/lib/systemimager/node-image.  This seems like it would make a
>>>>nice replica of my client system that SIS could then push out to other
>>>>nodes.
>>>>
>>>>Does anybody have any opinions on why this would or would not work?
>>>>       
>>>>
>>>you might run into ulimit issues creating a file the size of your hard
>>>drive...you CANNOT put that file on the hard drive that's the source...you
>>>could pipe it to another system across the network.  Remember, dd will
>>>also grab empty space....your 36 gig hard drive will produce a 36 gig
>>>file.
>>>
>>>     
>>>
>>>>Thanks,
>>>>Dan
>>>>       
>>>>
>

>

Reply via email to