Differences
This shows you the differences between two versions of the page.
| Last revision Both sides next revision | |||
|
debian_aoe_migrate [2007/08/24 14:42] bengen created aoebootprepdebianetch |
debian_aoe_migrate [2007/08/24 14:57] bengen point out choice of real disk or chrooted image |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Migrating Debian GNU/Linux 4.0 (etch) or later to an AoE target ====== | ====== Migrating Debian GNU/Linux 4.0 (etch) or later to an AoE target ====== | ||
| + | You can either work witha an installation | ||
| + | - that is running off a physical disk on a client machine or | ||
| + | - a loopback-mounted disk image running as a ''chroot(8)'' environment | ||
| Install the ''aoetools'' package and a kernel image that includes the | Install the ''aoetools'' package and a kernel image that includes the | ||
| Line 19: | Line 22: | ||
| FIXME Create/update ''/boot/grub/menu.lst'' | FIXME Create/update ''/boot/grub/menu.lst'' | ||
| - | You can now [[santransfer|transfer]] the contents of your physical | + | If the modifications were applied to a physical disk on the client |
| - | disk to an image stored on the SAN or continue by [[sanexport|making]] | + | machine, you can now [[santransfer|transfer]] the contents of your |
| - | the contents of your image available. | + | physical disk to the SAN target. |
| + | |||
| + | If the image you wish to export to client systems was modified directly,, | ||
| + | just make the contents of that image [[sanexport|available]]. | ||
| ==== Hints ==== | ==== Hints ==== | ||
