| Author |
Message |
|
|
Post subject:
 Posted: Jul 14, 2008 - 10:12 PM
|
|
Joined: Aug 24, 2007
Posts: 434
Location: Ljubljana
Status: Offline
|
|
The simplest solution is, say, just decide sidux be the main system, and install grub to MBR.
Then if you are kind of person who can't stand without trying other distro/os, just do it in vbox,
that is, always boot in sidux and do regular d-u. For me, multibootin is a trend of the past. 
When you try other distro for days/weeks with multibooting, you don't do regular d-u of sidux,
and your way back to sidux will be more difficult later. (of course, it's just my opinion.) |
|
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Jul 15, 2008 - 10:55 AM
|
|
Joined: May 02, 2008
Posts: 84
Status: Offline
|
|
| Can't play nice with other distros is generally not considered a plus... |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 02:54 PM
|
|
Joined: Jan 16, 2008
Posts: 90
Status: Offline
|
|
|
sleekmason wrote:
The best thing to do is just make a copy of your menu.lst for future installs.
Hard to say which is best about either loading all into 1 menu.lst or using the chainloader, but with all the changes and probs with grub it just seems to be the easiest solution to me to use the chainloader. I have done both and even used lilo before(another boot loader) with satisfaction.
As far as how to reinstall grub you may look here: http://manual.sidux.com/en/sys-admin-gr ... -grub-boot and search the forums for more specific problems. I believe I asked the same thing about 1 year ago, and I think I've seen it several times since.
I agree with you! I think I will use the chainloader method when I do a new system. My new HD has just come in the mail and it's a larger 320GB WD 3200AAKS drive which will be faster than my previous generation drive. I also have more room to install multiple OS's. I think I will use the multi-boot method instead of a virtual box for now.
How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it? I mean, I was looking for all the steps. I've read the manual but I find most manuals are all over the place including steps I won't use or need (I don't need the floppy instructions or lilo etc. etc.).
I'll try to google this and read the related sidux content in the manual in the meantime.
I am considering to have a brand new install of both Linux and Windows on the new drive (I made a slipstreamed XP SP2 CD w/ SATA drivers and am curious to see if it will work aka if I did it correctly).
But, for now, I would like to experiment on my current (see: old) drive as it is mostly OS stuff and not much data on it to backup (could be done quickly). Therefore, I thought I'd try re-installing XP and then try to reinstall grub. Right now, Debian Lenny is pointing to the grub.conf file (is that how to explain it?) so my menu.lst is there. I would like to back it up and then repair it. Debian doesn't have a liveCD.
When I build with my new HDD, I'll probably install grub to the MBR using the sidux LiveCD.
EDIT: I thought of another idea: I have some space left on the old drive. I could re-install XP which will wipe out grub (right?). I have a sidux liveCD already so I could install (after XP) to the leftover disk space and install to the MBR. That should fix everything?
However, I am curious how I would solve the issue by repairing Debian's grub menu.lst (method without a liveCD), though. Okay, 'just thought I'd offer that idea up.
Thanks for more info/assistance and followups to my posts! |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 03:22 PM
|
|
Joined: Dec 02, 2006
Posts: 1637
Location: Germany / NRW
Status: Offline
|
|
|
tuxracer wrote:
How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it? I mean, I was looking for all the steps. I've read the manual but I find most manuals are all over the place including steps I won't use or need (I don't need the floppy instructions or lilo etc. etc.).
Quote:
# cp -a /boot/grub/menu.lst /path/to/backup/menu.lst
I think you'll have something like an archiv or a backup partition, if not copy it to ~/safe/menu.lst or the like. The folder you copy the menu.lst to shouldn't be on the "/" partition/disk  . |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 03:27 PM
|
|
Joined: May 02, 2008
Posts: 84
Status: Offline
|
|
|
Quote:
How do I make a copy of my menu.lst for when my grub is messed up and I want to 'fix' it?
The trick is to make a copy before it's messed up...
In terminal:
Code:
su
cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
To restore the backup, do it in reverse, eg:
Code:
su
cp /boot/grub/menu.lst_backup /boot/grub/menu.lst
Of course, it won't do much good if your pc is unbootable in the first place. For that contingency/eventuality, better copy the backup to another media such as a floppy disk. Then you can boot from a livecd and restore it from there.
My comment about maintaining a full grub floppy still stands. Understand, though, that you can't just copy the menu.lst from a hdd grub installation, since full grub from a floppy will map the drives differently. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 03:59 PM
|
|
Joined: Jan 16, 2008
Posts: 90
Status: Offline
|
|
|
dsmithhfx wrote:
The trick is to make a copy before it's messed up...
In terminal:
Code:
su
cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
To restore the backup, do it in reverse, eg:
Code:
su
cp /boot/grub/menu.lst_backup /boot/grub/menu.lst
Of course, it won't do much good if your pc is unbootable in the first place. For that contingency/eventuality, better copy the backup to another media such as a floppy disk. Then you can boot from a livecd and restore it from there.
My comment about maintaining a full grub floppy still stands. Understand, though, that you can't just copy the menu.lst from a hdd grub installation, since full grub from a floppy will map the drives differently.
Thanks so much! That is the info I'm looking for. That code looks familiar. I'm sure I've read that before.
Could I use a USB flash drive instead of a floppy? That would be more convenient than going out and buying a floppy and then hooking that up.
[quote="michaa"]
Quote:
#
Code:
cp -a /boot/grub/menu.lst /path/to/backup/menu.lst
I think you'll have something like an archiv or a backup partition, if not copy it to ~/safe/menu.lst or the like. The folder you copy the menu.lst to shouldn't be on the "/" partition/disk .
Yes, true! I'm trying to learn of my options. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 10:01 PM
|
|
Joined: Aug 24, 2007
Posts: 434
Location: Ljubljana
Status: Offline
|
|
|
dsmithhfx wrote:
Can't play nice with other distros is generally not considered a plus...
but sidux is the most compatible to tomorrows distros. not with yesterdays...
muchan |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 15, 2008 - 11:17 PM
|
|
Joined: Jan 16, 2008
Posts: 90
Status: Offline
|
|
|
dsmithhfx wrote:
In terminal:
Code:
su
cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
To restore the backup, do it in reverse, eg:
Code:
su
cp /boot/grub/menu.lst_backup /boot/grub/menu.lst
I think I can use a usb flash drive for this?
I have read that they are often used to store a Linux OS but I just want to have a menu.lst file and any other related yet required files (if any).
That way, I could be using a liveCD to go into any distro's /boot/grub and use the menu.lst file on the usb flash drive to copy it over.... right?
The problem is I don't know linux enough to know how to do this and I was having problems with mounting/copying. I now have a 'menu.lst_backup' in my /boot/grub directory. Oops. I did manage to use the GUI way of copying (sorry, Windows) the file but I want to know how to do it the 'unix' terminal console or CL (command line?) method.
However, I am not sure whether I need to format the USB flash drive and to which format if I need to do this. I guess this topic should be in hardware now? I just thought it is a continuation of preparing an install and a 'safe fix' in case grub is ever "damaged.' I like to think I understand some part of what is going on but perhaps, someone can let me know whether this is a good strategy or not.
Btw, the usb flash drive is 8GB so I have much space to do this if it is a good option. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 16, 2008 - 02:14 AM
|
|
Joined: May 02, 2008
Posts: 84
Status: Offline
|
|
|
muchan wrote:
but sidux is the most compatible to tomorrows distros. not with yesterdays...
And... which do you suppose is more likely to be installed? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 16, 2008 - 12:14 PM
|
|
Joined: Aug 24, 2007
Posts: 434
Location: Ljubljana
Status: Offline
|
|
|
Quote:
The problem is I don't know linux enough to know how to do this and I was having problems with mounting/copying. I now have a 'menu.lst_backup' in my /boot/grub directory. Oops. I did manage to use the GUI way of copying (sorry, Windows) the file but I want to know how to do it the 'unix' terminal console or CL (command line?) method.
unix/linux command for copying file is cp.
cp source_file distination_name
or see the detailed usage with
man cp
or even better, read through the documentation of GNU coreutils by
info coreutils
or search a website for command line... like sidux manuals gives you a link to
http://linuxcommand.org/ |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 16, 2008 - 12:16 PM
|
|
Joined: Aug 24, 2007
Posts: 434
Location: Ljubljana
Status: Offline
|
|
|
Quote:
> but sidux is the most compatible to tomorrows distros. not with yesterdays... Wink
And... which do you suppose is more likely to be installed?
whatever... the current incompatibilty is simply a fact that sidux has newer version of Grub,
so tomorrow's distro/os that comes with newer Grub will be compatible with today's sidux. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 16, 2008 - 02:56 PM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 1857
Location: w3
Status: Offline
|
|
sidux is intended to be installed as your primary operating system, and therefore defaults to installing it's newest Grub to MBR. If done so, it will automaticly add entries for booting all other operating systems found. This usually works fine, and is the supported way of doing it. We recommend to tell all other operating systems to install their boot loaders into their respective partitions, and you should easily be able to chainload into them (even if they upgrade the boot loader, the kernel, ....). As sidux upgrades it's kernels quite often for very good reasons, this is the most practical solution.
For all those who insist in controlling the MBR not with sidux, but with another operating system - well, we do not chain you and offer the options to do so, but you are on your own, and definitely not supported here (as we do not want to support other operating systems, obviously). You will have to live with the bugs outdated Grub versions contain, or - even worse - with incompatibilities/inabilities other boot loaders come with.
Your freedom of choice - and ours!
Greetings,
Chris |
_________________
64bit stuff for sidux
development is life - code.zikula.org
an operating system must operate - sidux.com
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 05:42 AM
|
|
Joined: Jan 16, 2008
Posts: 90
Status: Offline
|
|
muchan, thanks for those instructions and advice. I will check those.
Quote:
sidux is intended to be installed as your primary operating system, and therefore defaults to installing it's newest Grub to MBR. If done so, it will automaticly add entries for booting all other operating systems found. This usually works fine, and is the supported way of doing it.
Hmmmm... I think I just want to experiment and choose a method! lol... I plan on having data on another drive anyway. I might experiment with VirtualBox, too, and sidux might make a good host for that?
Anyway, in response to your post and comments, I would like some additional info. Are you saying that a siduxinstall of grub to MBR will automatically boot up future distros if you install the respective grubs for those to their partition, that sidux will edit the menu.lst with the chain load for those? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 07:56 AM
|
|
Joined: Mar 26, 2008
Posts: 56
Location: Dresden / DE
Status: Offline
|
|
|
Quote:
Are you saying that a siduxinstall of grub to MBR will automatically boot up future distros if you install the respective grubs for those to their partition, that sidux will edit the menu.lst with the chain load for those?
That would be very nice, but afaik not possible.
Every OS that is installed after sidux gains a manually chainload-entry in the sidux menu.lst
Grub only recognizes already present OS on installation. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 08:15 AM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 1857
Location: w3
Status: Offline
|
|
The problem can be solved by creating a chainload entry for every partition where you plan to install other Linux distributions in your menu.list:
Code:
### END DEBIAN AUTOMAGIC KERNELS LIST
title testinstall (sda5)
chainloader (hd0,4)+1
title testinstall (sda6)
chainloader (hd0,5)+1
title testinstall (sda7)
chainloader (hd0,6)+1
title testinstall (sda8)
chainloader (hd0,7)+1
title testinstall (sda9)
chainloader (hd0,8)+1
That way you can boot all of them, even if they are installed later on. You may adapt the titles to better fit your needs.
Greetings,
Chris |
_________________
64bit stuff for sidux
development is life - code.zikula.org
an operating system must operate - sidux.com
|
| |
|
|
|
|
|
|
