| What are the restrictions ZENworks imaging puts on the way a machine is partitioned? | ||
|---|---|---|
 | Imaging Linux boxes with Zenworks imaging |  |
| What are the restrictions ZENworks imaging puts on the way a machine is partitioned? | ||
|---|---|---|
| | Imaging Linux boxes with Zenworks imaging | |
None. But if you want to restore, and have to do any partitioning (as is already the case if you have a swap partition -see previous answer-), then all tools you have are fdisk, sfdisk and the img program Novell provides. There are a few things I think should be repaired in the img program before it becomes useful[35]:
It cannot remove logical partitions (it can only remove the entire extended partitions).
It refuses to create swap partitions of sensible size, only succeeding if they are huge.
It sometimes goes into interactive mode when provided with command line parameters, thus making scripting hard.
It has a curses-like GUI, but the GUI sometimes stalls, not reflecting what is happening any more.
When restoring only a single partition from an image, it retrieves the entire image, and instead of just skipping over the entire lot, it checks every file in the image, and skips it if it isn't in the appropriate partition.
[35] I may be malinformed, but then the criticism in these lines goes straight back to the makers of the documentation on the program
| |  | |
| Imaging Linux boxes with Zenworks imaging |  | What limitations does ZENworks imaging impose on the filesystems used? |