Re: [IPCop-user] Testing latest 2.1.1 update
Eric Oberlander <[email protected]> Sun, 17 Nov 2013 17:53:50 +0000
| Newsgroups | gmane.comp.security.ipcop.devel |
|---|---|
| Message-ID | <CAPkz44FkffntET8NrZXJkRczmhb7TJK1SXrwjg-KmpsSwZqsiQ@mail.gmail.com> |
Oops, wrong list. Thanks for pointing that out David. Eric On 17 November 2013 17:33, David W Studeman <[email protected]> wrote: > On 11/17/2013 9:08 AM, Eric Oberlander wrote: > > Hi chaps > > > > I'm getting this error when I apply the 2.1.1 update to my IPCop v2.1 > > testbox: > > > > Boot configfile already has 3.4-1. > > Copying many modules. This may take some time .... Done > > Copying firmware ... Done > > Creating ipcoprd.img. This may take some time ... Done > > awk: error while loading shared libraries: libmpfr.so.1: cannot open > shared > > object file: No such file or directory > > ERROR: Not enough space on /boot. > > 2.1.1 update installed. > > > > Eric > > Did you mean this to be on the devel list? > > I was always wondering where the mechanism is that should be relinking > to the new kernel. I hadn't looked in updatekernel.pl in a while so I > cannot comment whether it is in that file. You really need to lose the > 3.0 kernel stuff as it will never be in any production version. How do > these updates fare when updating a 2.0.6 box? Yes, we fake out an > existing 2.1.1svn trunk build to test updates but it only counts if > 2.0.6 can be updated cleanly. > > On my Raqcop updates I actually include the symlinks to the kernel image > AND map in the update tarball. Since there is no bootloader on a Cobalt, > there is no reason to keep any old images since without symplinks they > will never boot so my updatekernel.pl is modified to remove the last one > and keep only the new one. On a Cobalt, the rom looks for vmlinux.gz or > vmlinux.bz2 only so I have to have said symlinks to the kernel image > which is named after the kernel version or it will never boot. > > Another thought would be to put fake 2.6.32 kernel image and > /lib/modules, move the 3.x stuff out of the way and see what happens. On > a standard IPCop, updatekernel.pl deletes old images except for the last > one so it would keep 2.6.32, add 3.4.x and go from there. > > -- > Dave Studeman > http://www.raqcop.com > > > > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk > _______________________________________________ > IPCop-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ipcop-user > ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ IPCop-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ipcop-devel