<br><br><div class="gmail_quote">On Sat, Mar 10, 2012 at 2:29 PM, Mikus Grinbergs <span dir="ltr"><<a href="mailto:mikus@bga.com">mikus@bga.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm just installing onto a jffs2 XO-1, no building, just an install, so I<br>
did the basics: an install then the copy. Did I miss something in the<br>
install that left the old files around?<br>
</blockquote>
<br>
Kevin - I've for years been removing the old files manually.<br>
<br>
What I do after the 'uname -r' is 'rpm -q kernel'. That gives me the full name of the kernel that is not running. Then I do 'rpm -e ...', specifying that obsolete kernel_full_name. I begin to finish up with 'find / -name ...' (where ... is a unique string extracted from the full name of the deleted kernel). Typically there will be leftover files within /versions/pristine/883 . I manually delete those. [In my opinion, the principal nand-space user is the leftover /lib/modules/,,, from the previous running system.]<br>
</blockquote><div><br>Thanks again very much Mikus. All works fine. Scripted the install and removes. Since this script is only run immediately after a full reflash to a vanilla 883, the names and locations are consistent. Cheers,<br>
<br>KG<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Of course, if the new kernel you installed did not come from a fully-functional rpm, then little things (like drivers) might stop working. If you wanted to no longer use the new kernel, but had deleted the previous kernel, you couldn't go back (e.g., by manually changing the pointers in the /boot directory <as used by OFW>) -- you would need to do a complete re-install.<span class="HOEnZb"><font color="#888888"><br>
<br>
mikus<br>
<br>
<br>
</font></span></blockquote></div><br>