I have 2 hdd's hda and hdb. I have RH 9 on hda2 w/ grub as bootloader. I then installed slackware 9 on hdb2 (which previously had RH 8.) hdb3 also has RH 8. Slackware is on reiserfs.
I have installed lilo of slackware on boot sector of / (hdb2) as I did not make a seperate boot partition.
I have copied the vmlinuz of slack to /boot of RH 9 and have made the entries in grub.conf as below:
----------------------------
default=0 timeout=10 splashimage=(hd0,1)/boot/grub/splash.xpm.gz title Red Hat Linux 9 (2.4.20-8) root (hd0,1) kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/12 hdd=ide-scsi initrd /boot/initrd-2.4.20-8.img title Slackware 9 (2.4.20) root (hd1,1) kernel /boot/vmlinuz-ide-2.4.20 ro hdd=ide-scsi title DOS rootnoverify (hd0,0) chainloader +1 ----------------------------
Now, when I try to boot into slackware from grub, it boots into RH 8 *even though it is pointing to the correct partition as grub recognises the reiserfs partition type*.
I can only boot into slackware thru the install CD with the root= option.
Previously, the original RH 8 loaded up from grub.
What am I doing wrong ? Why hasn't slackware overwritten the boot sector of it's root partition ?
I used to get pretty vague fs erors on this disk previously which is why I bought a new hdd and kept the old one as a backup.
regards,
Sharukh.
On Friday 25 Jul 2003 9:36 am, Dr. Sharukh K. R. Pavri. wrote:
I have 2 hdd's hda and hdb. I have RH 9 on hda2 w/ grub as bootloader. I then installed slackware 9 on hdb2 (which previously had RH 8.) hdb3 also has RH 8. Slackware is on reiserfs. I have installed lilo of slackware on boot sector of / (hdb2) as I did not make a seperate boot partition.
I have copied the vmlinuz of slack to /boot of RH 9 and have made the entries in grub.conf as below:
default=0 timeout=10 splashimage=(hd0,1)/boot/grub/splash.xpm.gz title Red Hat Linux 9 (2.4.20-8) root (hd0,1) kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/12 hdd=ide-scsi initrd /boot/initrd-2.4.20-8.img title Slackware 9 (2.4.20) root (hd1,1) kernel /boot/vmlinuz-ide-2.4.20 ro hdd=ide-scsi title DOS rootnoverify (hd0,0) chainloader +1
Now, when I try to boot into slackware from grub, it boots into RH 8 *even though it is pointing to the correct partition as grub recognises the reiserfs partition type*.
Sounds quite messy, why dont you get a bookfloppy like tomsrtbt, or boot into whatever linux is booting, and install lilo into mbr from scratch, that would be faster for me to do than trying to make sense of your situation.
BTW slackware dont have any initrd section? And BTW I usually advice lilo over grub, as lilo needs to be installed everytime lilo.conf change is to take effect, and lilo will crib if there is problem, whereas all the grub.conf problem is detected at boottime.
On Fri, 25 Jul 2003, Amit Upadhyay wrote:
Content-Description: signed data
On Friday 25 Jul 2003 9:36 am, Dr. Sharukh K. R. Pavri. wrote:
I have 2 hdd's hda and hdb. I have RH 9 on hda2 w/ grub as bootloader. I
<snip>
Sounds quite messy, why dont you get a bookfloppy like tomsrtbt, or boot into whatever linux is booting, and install lilo into mbr from scratch, that would be faster for me to do than trying to make sense of your situation.
But lilo is said to be soon deprecated.
BTW slackware dont have any initrd section? And BTW I usually advice lilo over
No slackware does not have an initrd.
grub, as lilo needs to be installed everytime lilo.conf change is to take effect, and lilo will crib if there is problem, whereas all the grub.conf problem is detected at boottime.
but grub does seem to be correctly set up. It *is* recognising the signature of the the reiserfs partition the somehow boots into RH which is supposed to have been wiped out :(.
Sharukh
On Friday 25 Jul 2003 11:04 pm, Dr. Sharukh K. R. Pavri. wrote:
On Fri, 25 Jul 2003, Amit Upadhyay wrote:
grub, as lilo needs to be installed everytime lilo.conf change is to take effect, and lilo will crib if there is problem, whereas all the grub.conf problem is detected at boottime.
but grub does seem to be correctly set up. It *is* recognising the signature of the the reiserfs partition the somehow boots into RH which is supposed to have been wiped out :(.
Wait a sec! From your mail I figured, its lilo that is taking control of boot and not grub, which now looks questionable. If by wipeed out you mean wiped out of the disk, you really need to see some baba, visit some local trains to get more details. But if you meant wiped out from the boot sequence setting, my guess would be you are not installing grub properly. I would say do a grub-install on your mbr again.
On Jul 25, 2003 at 23:04, Dr. Sharukh K. R. Pavri. wrote:
But lilo is said to be soon deprecated.
Cite?
On Fri, 25 Jul 2003, Satya wrote:
On Jul 25, 2003 at 23:04, Dr. Sharukh K. R. Pavri. wrote:
But lilo is said to be soon deprecated.
Cite?
Release notes of RH8 and RH9
Sharukh.
On Saturday 26 Jul 2003 10:17 pm, Dr. Sharukh K. R. Pavri. wrote:
On Fri, 25 Jul 2003, Satya wrote:
On Jul 25, 2003 at 23:04, Dr. Sharukh K. R. Pavri. wrote:
But lilo is said to be soon deprecated.
Cite?
Release notes of RH8 and RH9
Should you not refrain from spreading misinformation, and say the complete thing, which is: it is deprecated for Redhat only. Redhat is one thing I truely hate in linux world **. Anyways, if you are sincere, and are trying to help a person switch to linux, make sure they don't use grub as bootloader. They will experiment [if they wont it doesnt matter wether its a lilo or grub] and may misconfigure their grub.conf and render their system non-bootable. I have never seen anybody supplying wierd option at bootime, but have seen almost anyone using linux modifying their lilo/grub to add windows entries for example. Therefore dummy proofing configuration is much more important than the slight differance at boot time.
Why do you think one should use grub and not lilo?
[OT]
** Quoting current recommendations to people installing Redhat, as on, iitb.computers [a news group], which can be safely taken as the majority openion here[IITB]: "Make sure you dont install/unselect KDE when installing redhat from CDs and get the RPMs from so and so place after installation" I wonder what would a poor soul without access to IITB LAN do!
Appeal: One may live with Redhat, its linux after all, you can make it work the way you want, but for a new user, one should advice the best available distro. Mandrake is highest rated, while Redhat is the most hated one, be sincere when you pick.
On Jul 26, 2003 at 23:32, Amit Upadhyay wrote:
On Saturday 26 Jul 2003 10:17 pm, Dr. Sharukh K. R. Pavri. wrote:
On Fri, 25 Jul 2003, Satya wrote:
On Jul 25, 2003 at 23:04, Dr. Sharukh K. R. Pavri. wrote:
But lilo is said to be soon deprecated.
Cite?
Release notes of RH8 and RH9
Should you not refrain from spreading misinformation, and say the complete thing, which is: it is deprecated for Redhat only. Redhat is one thing I
Ah, that's what I was thinking. Thanks for the clarification.
On Sat, 26 Jul 2003, Amit Upadhyay wrote:
Content-Description: signed data
On Saturday 26 Jul 2003 10:17 pm, Dr. Sharukh K. R. Pavri. wrote:
On Fri, 25 Jul 2003, Satya wrote:
On Jul 25, 2003 at 23:04, Dr. Sharukh K. R. Pavri. wrote:
But lilo is said to be soon deprecated.
Cite?
Release notes of RH8 and RH9
Should you not refrain from spreading misinformation, and say the complete thing, which is: it is deprecated for Redhat only.
Ok, maybe mea culpa but I *had* mentioned that RH 9 was my primary OS :) So this is *not* misinformation. The fact that *you* did not know about it does not make it so.
Redhat is one thing I truely hate in linux world **.
Oh my god a religious fanatic, wow !! My dear chap, linux is *all about choice* you are free to hate redhat, no skin off my nose. I happen to use it and find it quite sufficient for my modest needs. If it ain't broke, don't fix it.
Anyways, if you are sincere, and are trying to help a person switch to linux, make sure they don't use grub as bootloader.
so the fact that I use grub makes me insincere ? you are almost on the verge of sermonising - tut tut. And I never said I was trying to get anyone to switch :-)
They will experiment [if they wont it doesnt matter wether its a lilo or grub] and may misconfigure their grub.conf and render their system non-bootable. I have never seen anybody supplying wierd option at bootime, but have seen almost anyone using linux modifying their lilo/grub to add windows entries for example. Therefore dummy proofing configuration is much more important than the slight differance at boot time.
This is just another of those cockamamie arguments of user friendliness vs geek power. Get a life boss. I want my os to work out of the box with as few tweaks as can be required. I am not into masochism and like to get on with my actual work of being a doctor. I'd rather read up for six hours on the complications of a septic gallbladder or the natural history of alzheimer's disease than spend it on some inane intricacy in my linux box *if it is not in the way of my normal routine work*.
And there's *nothing* wrong in experimentation and if you fall flat on your face, well you just have to get up, brush off the dirt and start again.
Why do you think one should use grub and not lilo?
why should *I* not use grub ?? I'm not asking you to change your bootloader, why do you expect me to change mine ? Like I said, it's a matter of choice.
[OT]
** Quoting current recommendations to people installing Redhat, as on, iitb.computers [a news group], which can be safely taken as the majority openion here[IITB]: "Make sure you dont install/unselect KDE when installing redhat from CDs and get the RPMs from so and so place after installation" I wonder what would a poor soul without access to IITB LAN do!
You know I fail to see the relevance of the above. Is it to point out that you are a member of the hallowed precincts of iitb ? in case someone just happened not to notice your email address ? or the six line signature at the end of your mail ? and there needs to be a '+' sign prefixed to the 91 of a cellular phone :)
I downloaded KDE 3 on a dial up link because *I wanted it*. This was sometime between the release of RH 7.2 and 7.3.
Appeal: One may live with Redhat, its linux after all, you can make it work the way you want, but for a new user, one should advice the best available distro. Mandrake is highest rated, while Redhat is the most hated one, be sincere when you pick.
I am *very* happy with redhat. I use it for word processing, email, web browsing, and a few other things. I had to patch ghostcript to get it to work w/ the latest hpijs to be able to use my new HP usb printer and I had to copile the beta of gphoto to be able to use my digital camera. I'd say I am quite happy w/ redhat.
Just because you couldn't get redhat to run does not mean you have to hate it. Stop being so opinionated. Keep your recommemdations of distros for someone who asks for it. Quit tilting at windmills Senor; remember what happened to Don Quixote :)
When you can hold forth on CAT scans and ECGs with the same aplomb that I can manage with a computer, we'll take this discussion to another level. Welcome to the Real World.
And don't take any of this personnally :-) ^^^ <-- smiley alert !!
-- Amit Upadhyay Senior Undergraduate Student Department of Mechanical Engg. Indian Institute of Technology Bombay Mumbai-76, India Phone: (91) 9820325940
Sharukh
Dr. Sharukh K. R. Pavri. writes:
And there's *nothing* wrong in experimentation and if you fall flat on your face, well you just have to get up, brush off the dirt and start again.
I am just fearful that the above words come from a doctor ;) They are not used to (human) systems crashing with any apparent reason. Methinks that makes find gnu/linux doctor friendly. :D
Vinayak Hegde
On Sun, 27 Jul 2003, vinayak_hegde@softhome.net wrote:
Dr. Sharukh K. R. Pavri. writes:
And there's *nothing* wrong in experimentation and if you fall flat on your face, well you just have to get up, brush off the dirt and start again.
I am just fearful that the above words come from a doctor ;)
so now you know who *not* to go to if you have a medical problem :)
They are not used to (human) systems crashing with any apparent reason.
^^^^ you mean without
Oh yes, human systems do crash seemingly without aparent reason -- look up SIDS (sudden infant death syndrome), AGBS (acute Guillain Barre syndrome), intra cranial arterio-venous malformations to name a few of the top of my head.
Methinks that makes find gnu/linux doctor friendly. :D
amen
Vinayak Hegde
Sharukh
On Jul 27, 2003 at 18:54, Dr. Sharukh K. R. Pavri. wrote:
the end of your mail ? and there needs to be a '+' sign prefixed to the 91 of a cellular phone :)
Any phone, not just cellular. AFAIK the + indicates that you should use your local system's escape codes to get an international line, and then dial the digits following the +. Those digits usually start with a country code. But whatever the digits, once you get past the +, you're not in your own system.
And don't take any of this personnally :-) ^^^ <-- smiley alert !!
A smiley! Yikes!
Doc, I recommend Debian. If you happen upon a point where your RH installation breaks, consider switching. I was using RH, and it was up to the point where the RPM DB was broken. Updates were a pain. For a few months, I irritated this list and another with ways to manually upgrade glibc -- something that I don't recommend to anyone except those listed in the kernel's credits file. That's when I switched to Debian. Maintainence is easiest.
On Sun, 27 Jul 2003, Satya wrote:
On Jul 27, 2003 at 18:54, Dr. Sharukh K. R. Pavri. wrote:
And don't take any of this personnally :-) ^^^ <-- smiley alert !!
A smiley! Yikes!
Doc, I recommend Debian. If you happen upon a point where your RH installation breaks, consider switching. I was using RH, and it was up to the point where the RPM DB was broken. Updates were a pain. For a few months, I irritated this list and another with ways to manually upgrade glibc -- something that I don't recommend to anyone except those listed in the kernel's credits file. That's when I switched to Debian. Maintainence is easiest.
Sure, point taken. I too had problems with the rpm db in RH8. I am using debian too on a different partition, but I am still not as comfortable with debian as with redhat at least at present. I intend trying out the knoppix install too.
I had a specific problem (in this case w/ a redhat *and* slackware install). I saw no reason for a rant about how bad redhat was.
It's just that I dislike this fanatical attitude that this distro is bad and this distro is good (heck or even that lilo is better than grub). What's wrong if it just works for me. You know I don't even know what glibc is, let alone wanting to change it :).
-- Satya. URL:http://satya.virtualave.net/ Don't use a big word where a diminutive one will suffice.
Sharukh.
---------- Original Message ----------- From: "Dr. Sharukh K. R. Pavri." spavri@vsnl.com To: Lug Bom linuxers@mm.ilug-bom.org.in Sent: Fri, 25 Jul 2003 09:36:36 +0530 Subject: [ILUG-BOM] multi-boot error w/ 2 hdd's
I have 2 hdd's hda and hdb. I have RH 9 on hda2 w/ grub as bootloader. I then installed slackware 9 on hdb2 (which previously had RH 8.) hdb3 also has RH 8. Slackware is on reiserfs.
I have installed lilo of slackware on boot sector of / (hdb2) as I did not make a seperate boot partition.
I have copied the vmlinuz of slack to /boot of RH 9 and have made the entries in grub.conf as below:
default=0 timeout=10 splashimage=(hd0,1)/boot/grub/splash.xpm.gz title Red Hat Linux 9 (2.4.20-8) root (hd0,1) kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/12 hdd=ide-scsi initrd /boot/initrd-2.4.20-8.img title Slackware 9 (2.4.20) root (hd1,1) kernel /boot/vmlinuz-ide-2.4.20 ro hdd=ide-scsi
^^^^^^
Why don't you try adding "root=/dev/hdb2" (or whatever is the root partition for your slackware install) in the above line and see if it boots correctly?
HTH, Rajen
-- Open WebMail Project (http://openwebmail.org)
On Fri, 25 Jul 2003, Rajen M. Parekh wrote:
---------- Original Message ----------- From: "Dr. Sharukh K. R. Pavri." spavri@vsnl.com
I have 2 hdd's hda and hdb. I have RH 9 on hda2 w/ grub as
<snip>
title Slackware 9 (2.4.20) root (hd1,1) kernel /boot/vmlinuz-ide-2.4.20 ro hdd=ide-scsi
^^^^^^Why don't you try adding "root=/dev/hdb2" (or whatever is the root partition for your slackware install) in the above line and see if it boots correctly?
No, tried that, doesn't work. Anyway, as I said, grub is pointing to the correct partition.
Sharukh
-
Amit Upadhyay -
Dr. Sharukh K. R. Pavri. -
Dr. Sharukh K. R. Pavri. -
Rajen M. Parekh -
Satya -
vinayak_hegde＠softhome.net