You are not logged in.
Pages: 1
experimenting with a few things and am looking to figure out how I can JUST install the boot loader.... via the ISO, it requires me to do all the steps before it (installing packages, partitioning, etc before I can install the boot loader. I'm looking for a way to essentially detect what's already there and skip all the other portions of the install process to JUST install the boot loader... anyone have any ideas where I can start? Searching the forums has not produced the specific thing I'm looking to do. A lot of stuff coverd about the bootloader in general, but not standalone installation of such. Thanks in advance!!!
Help grow the dev population... have your tech trained and certified!
Offline
You cannot just execute grub on the root prompt ?
Offline
Mount the volume you want to install it to and do a grub-install with the --root-directory parameter:
mount /dev/sda1 /mnt
grub-install --root-directory=/mnt /dev/sda
no place like /home
github
Offline
I think demian is along the lines I am working for... but why would I need to mount sda1 when I'm installing grub in sda? just curious...
Help grow the dev population... have your tech trained and certified!
Offline
grub-install is risky... better to boot to a live cd and load grub, set the root, then do a setup
# grub
<<Now you're in grub>>
>root (hdx,y)
>setup (hdx)
That will install grub to the MBR of hdx - you can also install grub to a partition if you want. See the grub wiki page.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
much appreciated... I will play with the info that graysky has offered and see where it gets me.... thanks again.
Help grow the dev population... have your tech trained and certified!
Offline
Let us know how it goes.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
most definitely!
Help grow the dev population... have your tech trained and certified!
Offline
within grub via most recent Arch iso:
---------
<grub> root (sda2)
Error 23: Error while parsing number
<grub> root (sda)
Error 23: Error while parsing number
<grub> setup (sda)
Error 23: Error while parsing number
---------
what am I doing wrong here?
Last edited by CPUnltd (2010-07-03 01:11:22)
Help grow the dev population... have your tech trained and certified!
Offline
grub uses hdx not sda
see my post or better yet the grub wiki page
http://wiki.archlinux.org/index.php/Grub
Last edited by graysky (2010-07-03 01:13:43)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
# grub <<Now you're in grub>> >root (hdx,y) >setup (hdx)
That will install grub to the MBR of hdx - you can also install grub to a partition if you want. See the grub wiki page.
Isn't that exactly what my line does? (grub-install --root-directory=/mnt /dev/sda)
@cpunltd: You have to mount a partition because Grub needs to know where to find the menu.lst and its other files. The package "grub" needs to be installed on /dev/sda1 in my example.
Last edited by demian (2010-07-03 09:20:30)
no place like /home
github
Offline
It is kind of, but as repeatedly stated, using grub-install has its risks, so it is recommended to use the grub shell.
From Grub Manual / Installing GRUB using grub-install:
Caution: This procedure is definitely less safe, because there are several ways in which your computer can become unbootable. For example, most operating systems don't tell GRUB how to map BIOS drives to OS devices correctly—GRUB merely guesses the mapping. This will succeed in most cases, but not always. Therefore, GRUB provides you with a map file called the device map, which you must fix if it is wrong. See Device map, for more details.
Offline
interesting... will have to test this tomorrow when I get back from work...
Help grow the dev population... have your tech trained and certified!
Offline
I think demian is along the lines I am working for... but why would I need to mount sda1 when I'm installing grub in sda? just curious...
Because the GRUB needs its files to be in /boot? Try removing your /boot/grub directory, and see what happens.*
* Only test if you can fix this and have the time for it
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Pages: 1