These problems should be fixed on newer versions. I think the danger still is present when you upgrade from 0.70<.
Scott On 9/16/05, Oliver Stark <[EMAIL PROTECTED]> wrote: > There seems to be definitely a glitch in the upgrade procedure, at least on > the older versions. Blank lines are inserted in the loader.rc making it grow > above a size where the loader cannot handle it any more. I guess, with a > file size of 784 bytes, you should be below this limit (Christian's > loader.rc was over 7kb, mine was over 14kb). Anyway, stripping out the blank > lines shouldn't cause you any harm. > > It might also be interesting that people with recent installs have a look at > their loader.rc just after upgrades to make sure that the newer versions > don't behave the same way. > > Oliver > > -----Original Message----- > From: Paulus Edwin Prasetya [mailto:[EMAIL PROTECTED] > Sent: September 16, 2005 1:07 AM > To: [email protected] > Subject: Re: [pfSense Support] Upgrade to 80.4 causes problems finding > kernel > > > Just reporting, this problem happen to me too. > > At first I installed version 74 and upgrading to 80.x > After 6 days, i try to reboot it, and reported kernel not found. > > Cause it is on production network, i do not have time to trace. > So i just re-installed the iso i had (v 74) and reconfuguring it > all manually. > I tried the configuration.xml I downloaded 1 day before, > it could not work. > > After all work properly, I upgraded it to 83.2 > and now the /boot/loader.rc is in size 784 > > i just tried: > # grep -v '^$' loader.rc > loader.rc.new > and have loader.rc.new is in size 346 > > So I think it is dangerous to reboot the gateway right now, > unless the problem is well known to be solved. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
