Re: SS5 install progressing, but have a question...
On Thu, Mar 11, 2004 at 08:32:35AM -0500, Schaefer, Robert (PS) wrote: > Okay, I've managed to get my SS5 to boot and start installing the system. > However, when I went to boot the live system after the base is installed, > I've hit my next snag. I had to set up the ever popular /boot partition due > to the 1gig bug, and Debian didn't correctly configure the system to boot > with this. So, since it was still looking for silo.conf in /etc, I'm stuck mv /etc/silo.conf /boot ln -s /boot/silo.conf /etc/ #probably don't need to do this vim /boot/silo.conf # make sure it is pointed at the /boot partition... silo -C /boot/silo.conf worked for me... it's probably a good idea to cd /boot ; ln -s /boot . > at a boot prompt. I know I can specify the name of the kernel image and the > root partition, but I don't know what the name of the kernel image is. So, > please help me with this information! Either that or was there a step I > missed in the install that would have allowed me to set it up correctly? the installer should do the above for you.. should probably file a bug on it... ls should work if it has the right partition, othwerwise you have to specify the drive... > I'm connecting through a serial console, and I don't think the alt-f keys > work, but I'm not sure. I don't mind starting over again at this point, but > would like to rescue this system if I can! Thanks for the help! boot the installer again and mount+chroot into your current installation. no reason to start over. -- -Justin
RE: SS5 install progressing, but have a question...
As long as /boot is not a separate mounted partition under /, no you won't need a separate /boot partition, since your root is less than 1gig. My problem stems from an older boot prom and following how Suse does things. (and how Debian implies things can be done, but doesn't correctly set things up, apparently) I'm trying to figure out what I did wrong in the setup, and how to boot the system as it stands now. Once I get it booted, I can fix the problem, its just getting it booted. I've since re-read stuff on silo, and see I can do an ls and see file names, so I'll try that tonight and see how far I can get. -Original Message- From: Peter [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 10:04 AM To: debian-sparc@lists.debian.org Subject: Re: SS5 install progressing, but have a question... On Thu, 2004-03-11 at 14:32, Schaefer, Robert (PS) wrote: > Okay, I've managed to get my SS5 to boot and start installing the > system. However, when I went to boot the live system after the base > is installed, I've hit my next snag. I had to set up the ever popular > /boot partition due to the 1gig bug, and Debian didn't correctly > configure the system to boot with this. So, since it was still > looking for silo.conf in /etc, I'm stuck at a boot prompt. I have set up the / partition on my SS5 to be 999MB and no /boot partition, (after I forgot the first time and I run into the same problem), and it works fine now. No need for a separate /boot I think? Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SS5 install progressing, but have a question...
On Thu, 2004-03-11 at 14:32, Schaefer, Robert (PS) wrote: > Okay, I've managed to get my SS5 to boot and start installing the > system. However, when I went to boot the live system after the base > is installed, I've hit my next snag. I had to set up the ever popular > /boot partition due to the 1gig bug, and Debian didn't correctly > configure the system to boot with this. So, since it was still > looking for silo.conf in /etc, I'm stuck at a boot prompt. I have set up the / partition on my SS5 to be 999MB and no /boot partition, (after I forgot the first time and I run into the same problem), and it works fine now. No need for a separate /boot I think? Peter
SS5 install progressing, but have a question...
Title: Message Okay, I've managed to get my SS5 to boot and start installing the system. However, when I went to boot the live system after the base is installed, I've hit my next snag. I had to set up the ever popular /boot partition due to the 1gig bug, and Debian didn't correctly configure the system to boot with this. So, since it was still looking for silo.conf in /etc, I'm stuck at a boot prompt. I know I can specify the name of the kernel image and the root partition, but I don't know what the name of the kernel image is. So, please help me with this information! Either that or was there a step I missed in the install that would have allowed me to set it up correctly? I'm connecting through a serial console, and I don't think the alt-f keys work, but I'm not sure. I don't mind starting over again at this point, but would like to rescue this system if I can! Thanks for the help! Bob SchaeferProQuest Automotivea subsidiary of ProQuest Business Solutions3900 Kinross Lakes ParkwayRichfield, OH 44286Phone: 330-659-1842work: [EMAIL PROTECTED]Home: [EMAIL PROTECTED] "Where's the Kaboom? There's supposed to be an Earth-shattering Kaboom!" - Marvin Martian "Hare-Way to the Stars"
