Revision 5aa25240 docs/usage.rst
b/docs/usage.rst | ||
---|---|---|
217 | 217 |
media or by using the *Bundle Host* button in the media selection dialog of |
218 | 218 |
snf-mkimage. During this operation, the files of the disk are copied into a |
219 | 219 |
temporary image file, which means that the file system that will host the |
220 |
temporary image needs to have a lot of free space (see `the tmpdir option`_
|
|
220 |
temporary image needs to have a lot of free space (see `large temporary files`_
|
|
221 | 221 |
for more information). |
222 | 222 |
|
223 | 223 |
Creating a new image |
... | ... | |
281 | 281 |
|
282 | 282 |
Choosing *YES* will create and upload the image to your *~okeanos* account. |
283 | 283 |
|
284 |
Some caveats on image creation |
|
285 |
============================== |
|
284 |
Limitations |
|
285 |
=========== |
|
286 |
|
|
287 |
Supported operating systems |
|
288 |
--------------------------- |
|
289 |
|
|
290 |
*snf-image-creator* can only fully function on input media hosting *Linux* |
|
291 |
systems. The program will detect the needed metadata and you may use it to |
|
292 |
upload and register other *Unix* or *Windows* images, but you cannot use it to |
|
293 |
shrink them or perform system preparation operations. |
|
294 |
|
|
295 |
Logical Volumes |
|
296 |
--------------- |
|
297 |
|
|
298 |
The program cannot work on LVM partitions [#f1]_. The input media may only |
|
299 |
contain primary or logical partitions. |
|
286 | 300 |
|
287 | 301 |
Para-virtualized drivers |
288 | 302 |
------------------------ |
... | ... | |
298 | 312 |
Many popular Linux distributions, like Ubuntu and Debian, will automatically |
299 | 313 |
create a generic initial ramdisk file that contains many different modules, |
300 | 314 |
including the VirtIO drivers. Others that target more experienced users, like |
301 |
Slackware, won't do that [#f1]_. *snf-image-creator* cannot resolve this kind
|
|
315 |
Slackware, won't do that [#f2]_. *snf-image-creator* cannot resolve this kind
|
|
302 | 316 |
of problems and it's left to the user to do so. Please refer to your |
303 | 317 |
distribution's documentation for more information on this. You can always check |
304 | 318 |
if a system can boot with para-virtualized disk controller by launching it with |
305 | 319 |
kvm using the *if=virtio* option (see the kvm command in the |
306 | 320 |
`Creating a new image`_ section). |
307 | 321 |
|
322 |
Some caveats on image creation |
|
323 |
============================== |
|
324 |
|
|
308 | 325 |
Image partition schemes and shrinking |
309 | 326 |
------------------------------------- |
310 | 327 |
|
... | ... | |
322 | 339 |
partition placed as the last partition on the disk and have your largest |
323 | 340 |
partition (*/* or */home*) just before that. |
324 | 341 |
|
325 |
The tmpdir option
|
|
326 |
----------------- |
|
342 |
Large temporary files
|
|
343 |
---------------------
|
|
327 | 344 |
|
328 | 345 |
*snf-image-creator* may create large temporary files when running: |
329 | 346 |
|
... | ... | |
343 | 360 |
|
344 | 361 |
.. rubric:: Footnotes |
345 | 362 |
|
346 |
.. [#f1] http://mirrors.slackware.com/slackware/slackware-14.0/README.initrd |
|
363 |
.. [#f1] http://sourceware.org/lvm2/ |
|
364 |
.. [#f2] http://mirrors.slackware.com/slackware/slackware-14.0/README.initrd |
Also available in: Unified diff