# /usr/local/bin/grub-mkimage --help Usage: /usr/local/bin/grub-mkimage [OPTION]... [MODULES] Make a bootable image of GRUB. -d, --directory=DIR use images and modules under DIR [default=/usr/local/lib/grub/i386-pc] -p, --prefix=DIR set grub_prefix directory [default=/boot/grub] -m, --memdisk=FILE embed FILE as a memdisk image -f, --font=FILE embed FILE as a boot font -c, --config=FILE embed FILE as boot config -o, --output=FILE output a generated image to FILE [default=stdout] -h, --help display this message and exit -V, --version print version information and exit -v, --verbose print verbose messages is the modules list just space separated? # /usr/local/sbin/grub-setup --help Usage: /usr/local/sbin/grub-setup [OPTION]... DEVICE Set up images to boot from DEVICE. DEVICE must be a GRUB device (e.g. `(hd0,1)'). -b, --boot-image=FILE use FILE as the boot image [default=boot.img] -c, --core-image=FILE use FILE as the core image [default=core.img] -d, --directory=DIR use GRUB files in the directory DIR [default=/boot/grub] -m, --device-map=FILE use FILE as the device map [default=/boot/grub/device.map] -r, --root-device=DEV use DEV as the root device [default=guessed] -f, --force install even if problems are detected -s, --skip-fs-probe do not probe for filesystems in DEVICE -h, --help display this message and exit -V, --version print version information and exit -v, --verbose print verbose messages the -s format of --skip-fs-probe doesn't seem to work + When I try to point to a core file using --core-image=/somepath/mycore.img grub tries to append the given path to /boot/grub/ eventhough it's given as a fully qualified path. In this case it becomes /boot.grub//somepath/mycore.img So while mkimage allows me to have the core.img written anywhere grub-setup will only accept it under /boot/grub/ _______________________________________________ Help-grub mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-grub
