Sollte eine anpassung an das Script nicht genug sein?
PHP-Code:
Hetzner Online AG
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────── NOTICE ──────────────────────────────────┐
│ │
│ An editor will now show you the config for the image. │
│ You can edit the parameters for your needs. │
│ To accept all changes and continue the installation │
│ just save and exit the editor with F10. │
│ │
│ Please note: by default all disks are used for software raid │
│ change this to (SWRAID 0) if you want to leave your other harddisk(s) │
│ untouched! │
│ │
├─────────────────────────────────────────────────────────────────────────┤
│ < OK > │
└─────────────────────────────────────────────────────────────────────────┘
## ====================
## HARD DISK DRIVE(S):
## ====================
DRIVE1 /dev/sda
DRIVE2 /dev/sdb
## ================
## SOFTWARE RAID:
## ================
## activate software RAID? < 0 | 1 >
SWRAID 0
## Choose the level for the software RAID < 0 | 1 >
SWRAIDLEVEL 0
## ============
## BOOTLOADER:
## ============
## Do not change. This image does not include or support lilo (grub only)!:
BOOTLOADER grub
## ==========
## HOSTNAME:
## ==========
## which hostname should be set?
##
HOSTNAME Ubuntu-1310-saucy-64-minimal
## ==========================
## PARTITIONS / FILESYSTEMS:
## ==========================
## define your partitions and filesystems like this:
##
## PART <mountpoint/lvm> <filesystem/VG> <size in MB>
##
## * <mountpoint/lvm> mountpoint for this filesystem *OR* keyword 'lvm'
## to use this PART as volume group (VG) for LVM
## * <filesystem/VG> can be ext2, ext3, reiserfs, xfs, swap *OR* name
## of the LVM volume group (VG), if this PART is a VG
## * <size> you can use the keyword 'all' to assign all the
## remaining space of the drive to the *last* partition.
## you can use M/G/T for unit specification in MIB/GIB/TIB
##
## notes:
## - extended partitions are created automatically
## - '/boot' cannot be on a xfs filesystem!
## - '/boot' cannot be on LVM!
## - when using software RAID 0, you need a '/boot' partition
##
## example without LVM (default):
## -> 4GB swapspace
## -> 512MB /boot
## -> 10GB /
## -> 5GB /tmp
## -> all the rest to /home
#PART swap swap 4096
#PART /boot ext2 512
#PART / reiserfs 10240
#PART /tmp xfs 5120
#PART /home ext3 all
#
##
## to activate LVM, you have to define volume groups and logical volumes
##
## example with LVM:
##
## logical volume definitions:
#LV <VG> <name> <mount> <filesystem> <size>
#
#LV vg0 root / ext3 10G
#LV vg0 swap swap swap 4G
#LV vg0 tmp /tmp reiserfs 5G
#LV vg0 home /home xfs 20G
#
#
## your system has the following devices:
#
# Disk /dev/sdb: 2000.4 GB (=> 1907 GIB)
# Disk /dev/sda: 2000.4 GB (=> 1907 GIB)
#
## Based on your disks and which RAID level you will choose you have
## the following free space to allocate (in GiB):
# RAID 0: ~3726
# RAID 1: ~1863
#
PART swap swap 16G
PART /boot ext3 512M
PART /ext4 all
## ========================
## OPERATING SYSTEM IMAGE:
## ========================
## full path to the operating system image
## supported image sources: local dir, ftp, http, nfs
## supported image types: tar, tar.gz, tar.bz, tar.bz2, tar.xz, tgz, tbz, txz
## examples:
#
# local: /path/to/image/filename.tar.gz
# ftp: ftp://<user>:<password>@hostname/path/to/image/filename.tar.bz2
# http: http://<user>:<password>@hostname/path/to/image/filename.tbz
# https: https://<user>:<password>@hostname/path/to/image/filename.tbz
# nfs: hostname:/path/to/image/filename.tgz
#
# for validation of the image, place the detached gpg-signature
# and your public key in the same directory as your image file.
# naming examples:
# signature: filename.tar.bz2.sig
# public key: public-key.asc
IMAGE /root/.oldroot/nfs/install/../images/Ubuntu-1310-saucy-64-minimal.tar.gz
oder muss ich alles von hand ändern?