Mailinglist Archive: opensuse (1390 mails)
| < Previous | Next > |
Re: Boot configuration. Was Re: [opensuse] Internet monitoring tool
- From: Dave Howorth <dhoworth@xxxxxxxxxxxxxxxxx>
- Date: Tue, 02 Mar 2010 14:35:14 +0000
- Message-id: <4B8D2222.5040401@xxxxxxxxxxxxxxxxx>
Anton Aylward wrote:
I've got that T-shirt! :( It's frustrating, isn't it? Even if you think
you might understand it, there's no way (that I've found) to see what
commands are actually going to be executed. And there are so many
different menus/buttons scattered around that screen, you have no
confidence in how they might interact.
I just abandoned the whole GUI idea and went back to the command line.
Even then you have to be very careful about the device map and about
which kernel is running whilst you do things.
Step 1 is to read the grub manual!
Well /boot is used by grub. So the whole concept of mount is irrelevant.
You need to have a *consistent* set of whatever files grub needs to boot
your system.
Which documentation? (hd0,5) is the *second* extended partition - see
http://www.gnu.org/software/grub/manual/html_node/Naming-convention.html
Grub's 'find' command is very useful for confirming what it thinks the
partition is called - http://www.gnu.org/software/grub/manual/grub.html#find
But again, be very careful of the device map.
Cheers, Dave
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Its not that 1-click kind of stuff I have problems with, not 'terms' as
such but concepts and expressions.
Right now I'm trying to find out how to move /boot to another partition
and make it work.
I have questions like ...
The screen at "yast -> System -> Boot Loader Settings", tab "Boot loader
Installation" has a number of check-off boxes
[ ] Boot from Master Boot Record
[ ] Boot from Root partition
[ ] Boot from Boot partition
[ ] Boot from Extended partition
[ ] Custom Boot partition
I've got that T-shirt! :( It's frustrating, isn't it? Even if you think
you might understand it, there's no way (that I've found) to see what
commands are actually going to be executed. And there are so many
different menus/buttons scattered around that screen, you have no
confidence in how they might interact.
I just abandoned the whole GUI idea and went back to the command line.
Even then you have to be very careful about the device map and about
which kernel is running whilst you do things.
Step 1 is to read the grub manual!
When I installed I had /boot in a regular partition and /root in an...
extended partition. I'm trying to set up a new /boot partition as
regular partition.
If I use the Custom box to specify my newly created partition do I have
to copy all of the old /boot over to the new partition? what about
changing its mount?
Well /boot is used by grub. So the whole concept of mount is irrelevant.
You need to have a *consistent* set of whatever files grub needs to boot
your system.
No, that can't be right, the old /boot/grub/menu.lst specified
root (hd0,5) all over the place. I *think* that means the first
partition in the extended partition, the extended being counted as #4 -
yes I found that in the documentation.
Which documentation? (hd0,5) is the *second* extended partition - see
http://www.gnu.org/software/grub/manual/html_node/Naming-convention.html
Grub's 'find' command is very useful for confirming what it thinks the
partition is called - http://www.gnu.org/software/grub/manual/grub.html#find
But again, be very careful of the device map.
Cheers, Dave
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |