On Wed, Dec 14, 2005 at 10:39:24AM -0800, Daniel B. Thurman wrote: > >I have everything installed in a single large partition. Why is it, > >that this was not a problem in the previous releases until now? Why > >the requirement that /boot be in it's own partition? This makes no > >real sense to me other than to protect partitions from one another or > >for performance concerns but if I choose to put everything in one > >partition, why not? Perhaps you are telling me that pervious releases > >just *happened* to work until the /boot files were no longer guaranteed > >to be in the lower partition space due to changes and/or kernel updates > >that it has creeped outside of the BIOS ability to read files beyond a > >certain size limitiation, i.e. the inodes are outside of it's > >bit-range? > > I forgot to add: I am ABLE to use the PREVIOUS kernel version to > boot my linux system - so WHY does this one work and not the current > one!?!?!? As you guessed, it 'just happened to work'. You've probably just filled up the early cylinders on your /boot So earlier kernels were fine, its only the new ones that push you past that limit. You might be able to get away with removing some of the earlier kernels to reclaim the lower cylinders, and then reinstall the latest kernel. Dave
