Yep, only from 0.95ish + upgrades.

On 12/15/05, John Cianfarani <[EMAIL PROTECTED]> wrote:
> Is this only required if you upgraded?
> All my installs were a reflash.
>
> Thanks
> John
>
> -----Original Message-----
> From: Scott Ullrich [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 15, 2005 2:45 PM
> To: [email protected]
> Subject: Re: [pfSense Support] ipsec issues
>
> Yep, that's exactly what is going on.   Just delete the old kernel
> file and install the new firmware.
>
> In terms of the older files elsewhere, I'd play it safe and not touch
> them for the time being.
>
> If you're really concerned with stale files, a reinstall is the correct
> answer.
>
> Scott
>
> On 12/15/05, Vivek Khera <[EMAIL PROTECTED]> wrote:
> > On Dec 15, 2005, at 1:29 PM, Scott Ullrich wrote:
> >
> > > Somethings not correct here.  We are well past RC1.
> >
> > inneresting... my 0.96.2 upgraded box also has the same uname -a
> output.
> >
> > A bunch of modules in /boot/kernel are dated december 11, but the
> > kernel file and a bunch of other modules are dated october 22...
> >
> > OOOOOHHHHH I see it.  We now install /boot/kernel.gz (dated december
> > 11) but the loader is picking up the older uncompressed version.
> > Looks like the upgrade should delete the older kernel...
> >
> > I suspect the right thing to do on upgrade is a similar thing that
> > "make installkernel" does to move /boot/kernel to /boot/kernel.old
> > and update some sysctl values to tell the system that's the booted
> > kernel.  This way /boot/kernel will be exactly the current kernel no
> > more no less.
> >
> >
> >
> > additionally,
> >
> > /usr/bin has some october 22 dated files: yp*, usb*, dig, and host.
> > /usr/libexec has some older files too.
> >
> > Can these outdated files just be deleted?  Seems like they are not
> > used at all.  On a normal freebsd install I'd just delete any non-
> > updated files like these.
> >
> > The only risk with deleting old libs from /lib or /usr/lib is that
> > some older packages may be linked against older libc's.
> >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to