---- Begin Original Message ---- From: Sent: Sun, 20 Dec 1998 10:28:36 -0500 To: Subject: Re: [SuSE Linux] yast & lilo linux linux wrote:
Can someone tell me why yast can not configure lilo correctly with large HDD's (1024 limit)? I can edit the lilo.conf file and run lilo myself with no problems. I think this is something that should be fixed in yast. thanks, krupps
this is silly eh?
;The 1024 cylinder limit comes from the fact that most bioses ;are still 16-bit. 2 to the 16th power is 1024. So the address ;must be less than 1024. I guess I didn't make myself clear. I understand what the 1024 limit is. I did what the SDB said to do... that is to make a 2mb partiton mounted at /boot. I had no problems installing at all, everything went smooth... It setup lilo with not snags at all. The problem came about when i wanted to compile my own kernel and install via yast. Yast kept reporting that the hdd was too large (the 1024 limit error message) and it refused to setup the kernel. At this point I simply got out of yast, fired up emacs (actually jove:), and edited the lilo.conf myself. All I had to do was change the kernel to be booted. After that I typed 'lilo' at the prompt and it accepted it. I guess what I really wanted to know was why yast couldn't do such a simple task. There should be an option or something to force it to accept the kernel. ;Getting a foolproof lilo setup going is not that easy. ;The 1024 cylinder limit provides a foolproof way of making ;sure lilo will work, but there are other ways depending on the ;system. ;It may work for you , but not someone else. ;I tried to install lilo a bunch of times, then I would swap ;hard drives, and lilo would stop working. ;Redhat's manual says the same thing, that if you observe the ;1024 limit, it will work for sure; BUT if you violate that ;limit, lilo MAY work for you, but it is not supported, since there ;are so many variables, that tech support can't deal with it. ;There is 1 foolproof method that I know of. ;Create a 1 sector (bare minimum) primary partition ;as the first partition on /dev/hda. ;Mount /boot there, and put your kernels in there. It will ;boot systems anywhere. My kernel still resides in the / directory. Sorry for not being clear. I'm not much of a writer. thanks, Joe aka krupps ;But many people do not want to have a primary partition ;wasted on this. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> ---- End Original Message ---- this is silly eh? ___________________________________________________________ Get your own Web-Based E-mail Service at <A HREF="http://www.zzn.com"><A HREF="http://www.zzn.com</A">http://www.zzn.com</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>