On Thu, Jun 06, 2002 at 03:33:07PM +0200, Kim Oppalfens said:
> Comments inline
>
> >
> > > Afterwards I get a working initrd.lrp.
> > >
> > > Now for the question, have you ever tried backing up your initrd.lrp.
> > > Even after changing the obvious 2.0.7 values in initrd.list with the 2.2.5
> > > ones it is a no go.
> > > It doesn't work for me the package gets smaller, something is going wrong
> > > with the links
> > > and with backing up the content of /var/lib/lrpkg
> >
> >Does it work in standard Bering? I had noticed that it didn't work, but
> >I'd assumed that it probably didn't work in stock Bering either -
> >initrd.lrp has a totally different format to a standard lrp file, and it
> >wouldn't suprise me if it couldn't be backed up via the standard
> >mechanism. I've not needed to make changes to my initrd.lrp very often,
> >so I've made them to the source tree on my dev box, rather than live on
> >the routers.
>
> I think it does, I think (not really sure anymore) I made modifications on
> the firewall to make it boot off of a cd or a hdd module.
>
> I think the problem might have something todo with the file being called
> initrd-new.img
I don't think so - I rename mine back to initrd.img, and I get:
Package Type BkupDev BkupFS Package Type BkupDev BkupFS
-------- ---- -------- -------- -------- ---- ----------------
1) init Full ram0 root 2) root Full hdc1 msdos
3) etc Full hdc1 msdos 4) log Full hdc1 msdos
when I run the backup, I get:
Selection: 1
cat: /var/lib/lrpkg/init.list: No such file or directory
Creating init.lrp Please wait: \tar: /tmp/EXCLUDE: No such file or
directory
looks to me like the menu is trying to backup a package called init.lrp,
when it's really initrd.lrp. The bit I don't understand is where it's
getting the init.lrp from - it's not in /var/lib/lrpkg/backdisk.
> I don't really know though, I think we will need the bering crew to fix
> this one.
I suspect so.
Cheers
Si
> > >
> > >
> > >
> > >
> > >
> > > >Rudimentary docs and packages to bring Bering up to glibc 2.2.5 are on
> > > >
> > > >http://www.wix.net.nz/LEAF/
> > > >
> > > >All input welcome - I'd especially like a few people to take them for a
> > > >spin before they get announced on the LEAF website or on 'users. Of
> > > >interest to note is that my sizing below was way out of wack - if you're
> > > >careful, the size difference isn't enormous:
> > > >
> > > >original: initrd.lrp 405K root.lrp 309K
> > > >glibc2.2: initrd.lrp 653K root.lrp 326K
> > > >
> > > >A total size increase of just 265K, which may make it workable in dual
> > > >floppy situations.
> > > >
> > > >Cheers
> > > >Si
> > > >
> > > >On Sat, Apr 27, 2002 at 06:00:22PM +1200, Simon Blake said:
> > > > > Sure - in the next couple of days I was going to do the same conversion
> > > > > to Bering RC2 and document the process for my own records. Once I've
> > > > > done that, I'll certainly put both changed packages and
> > documentation up
> > > > > somewhere.
> > > > >
> > > > > Cheers
> > > > > Si
> > > > >
> > > > > On Fri, Apr 26, 2002 at 06:39:39PM +0200, Kim Oppalfens said:
> > > > >
> > > > > > At 13:09 26/04/2002, Simon Blake wrote:
> > > > > >
> > > > > >
> > > > > > Would indeed make it to large for a single floppy release, but not
> > > > for many
> > > > > > of us that run dual floppy, flash, hdd or cdrom
> > > > > > based leaf's. So it there any chance you can post the packages
> > > > somewhere?
> > > > > > And maybe just maybe, if you can spare the time write a little
> > > > > > step-by-step document explaining what you did?
> > > > > >
> > > > > > I know I would appreciate very much, and I expect I am not the
> > only one
> > > > > >
> > > > > > Kim
> > > > > >
> > > > > > >Hi folks
> > > > > > >
> > > > > > >Nothing quite like replying to yourself a month later. A few
> > weeks ago,
> > > > > > >I had another go at converting Bering to glibc 2.2.5, and
> > irritatingly,
> > > > > > >it pretty much worked first time :-). I've now got a couple of
> > routers
> > > > > > >out in the field running Bering RC1 and glibc 2.2.5, and it seems
> > > > > > >to be working a charm. For those that asked, the increase in bloat
> > > > > > >probably rules out single floppy systems, but it's not enormous:
> > > > > > >
> > > > > > >Original Bering:
> > > > > > >-rwxr-xr-x 1 root root 409022 Mar 19 00:56 initrd.lrp
> > > > > > >-rwxr-xr-x 1 root root 317849 Mar 22 01:22 root.lrp
> > > > > > >
> > > > > > >Glib2.2 Bering:
> > > > > > >-rwxr-xr-x 1 root root 916546 Apr 9 00:08 initrd.lrp
> > > > > > >-rwxr-xr-x 1 root root 380303 Apr 8 23:02 root.lrp
> > > > > > >
> > > > > > >About the only trap in the transition is that you have to
> > increase the
> > > > > > >size of the minix file system in initrd.lrp and of the initial
> > ramdisk
> > > > > > >to accomodate the bloat.
> > > > > > >
> > > > > > >Cheers
> > > > > > >Si
> > > > > > >
> > > > > > >On Wed, Mar 20, 2002 at 01:45:55PM +1200, Simon Blake said:
> > > > > > >
> > > > > > > > Hi Folks
> > > > > > > >
> > > > > > > > I've been using Dachstein with a home grown upgrade to libc
> > v2.2.4
> > > > > > > > (simply replacing most of /lib in root.lrp with the files
> > from my
> > > > debian
> > > > > > > > unstable box) - works a charm, and since I'm working of
> > Compact Flash
> > > > > > > > the extra bloat isn't a huge issue. It makes packaging easier
> > > > (no need
> > > > > > > > to keep an old dev env around), and makes some otherwise
> > uncompilable
> > > > > > > > code accessible (notably vrrpd and some of the LVS stuff).
> > > > > > > >
> > > > > > > > So, I've tried the same thing with Bering - upgraded libc and
> > > > ld-linux
> > > > > > > > in initrd.lrp, and the rest of /lib in root.lib. It all
> > seems to
> > > > work,
> > > > > > > > except that root can no longer login (gets an error about
> > UNKNOWN
> > > > user
> > > > > > > > on tty1). Now, I'm aware that that's probably not a Bering
> > specific
> > > > > > > > error, but I'm wondering if anybody else has done something
> > like this
> > > > > > > > and solved this problem, before I dive in and try and fix it
> > myself.
> > > > > > > > Are there plans for a libc2.2 based Bering?
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > > Si
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Leaf-devel mailing list
> > > > > > > > [EMAIL PROTECTED]
> > > > > > > > https://lists.sourceforge.net/lists/listinfo/leaf-devel
> > > > > > >
> > > > > > >_______________________________________________
> > > > > > >Leaf-devel mailing list
> > > > > > >[EMAIL PROTECTED]
> > > > > > >https://lists.sourceforge.net/lists/listinfo/leaf-devel
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Leaf-devel mailing list
> > > > > [EMAIL PROTECTED]
> > > > > https://lists.sourceforge.net/lists/listinfo/leaf-devel
> > > >
> > > >_______________________________________________________________
> > > >
> > > >Have big pipes? SourceForge.net is looking for download mirrors. We supply
> > > >the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> > > >
> > > >_______________________________________________
> > > >Leaf-devel mailing list
> > > >[EMAIL PROTECTED]
> > > >https://lists.sourceforge.net/lists/listinfo/leaf-devel
> > >
> > >
> > > _______________________________________________________________
> > >
> > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> > >
> > >
> > > _______________________________________________
> > > Leaf-devel mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/leaf-devel
> >
> >_______________________________________________________________
> >
> >Don't miss the 2002 Sprint PCS Application Developer's Conference
> >August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> >
> >
> >_______________________________________________
> >Leaf-devel mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
----- End forwarded message -----
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
