Expanded Imager
0 views
Skip to first unread message
Billy Ayotte
Sep 29, 2011, 9:29:50 AM9/29/11
to open1to1discussion
So I've made some more headway with my imaging script. I can now
repartition the disk properly. One thing that has always bugged me
about the Open1to1 imager is that it is limited and rather inflexible.
For example for some reason it refuses to image my machines. To make
matters worse I can't debug the imager since the source doesn't seem
to be available (at least I couldn't find it).
So I made a script that uses the existing applications on the pendrive
to replicate most of the functions of the open1to1 imager. This worked
rather well and it gave me the ability to debug and alter the script.
Now that our deployment is largely over I'm looking to expand the
functionality to encompass ntfs imaging.
The only issue I'm having is the script still needs to be called
manually from another terminal. Is there a way to make a script
autorun instead of the Open1to1 imager?
repartition the disk properly. One thing that has always bugged me
about the Open1to1 imager is that it is limited and rather inflexible.
For example for some reason it refuses to image my machines. To make
matters worse I can't debug the imager since the source doesn't seem
to be available (at least I couldn't find it).
So I made a script that uses the existing applications on the pendrive
to replicate most of the functions of the open1to1 imager. This worked
rather well and it gave me the ability to debug and alter the script.
Now that our deployment is largely over I'm looking to expand the
functionality to encompass ntfs imaging.
The only issue I'm having is the script still needs to be called
manually from another terminal. Is there a way to make a script
autorun instead of the Open1to1 imager?
David Trask
Sep 29, 2011, 9:35:00 AM9/29/11
to open1to1d...@googlegroups.com
Gonna have to ask Brendan on that one ;-) The Open1to1 imager was designed to do one thing and one thing well. Image. I wish I knew what was going on in your case. There have been no other reported instances of folks not being able to image the 1005HA's. it works fine. Randy was able to do all of his without any hiccup. Nonetheless....please share your work when you can....maybe we can all expand on it and incorporate it into the next generation.
--
You received this message because you are subscribed to the Google Groups "open1to1discussion" group.
To post to this group, send email to open1to1d...@googlegroups.com.
To unsubscribe from this group, send email to open1to1discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/open1to1discussion?hl=en.
Brendan Powers
Sep 29, 2011, 10:38:04 AM9/29/11
to open1to1d...@googlegroups.com
You can find the source code repository here https://bitbucket.org/resara/open-1-1
It contains the latest open1to1 code, except for some EFI work I haven't commited yet. In order to launch another script at boot time, you will need to modify the initrd. At some point I need to look into why the imager isn't working for you.
The open1to1 imager was designed to do one thing very quickly. However, it's fairly easy to modify it to do other things. For example, I created a modified version for use at Resara that would create and image raid arrays.
Reply all
Reply to author
Forward
0 new messages