Hello SImon, Kim and others on this thread. First of all sorry for the late response of the "bering crew". Jacques is out of town for the rest of this week, and I just ended a 24 Hr shift , so i wasn't able to read the mails.
To answer a few questions. The lrpkg.back.script is name dependent. With the usual *.list etc is a include and exclude file list created. Before the create and compress the tar file command is executed, there is a statement like If the name is initrd. then gzip the image and write it to initrd.lrp otherwise create a tar file and gzip it. I planned a "rewrite of the script" but jacques and I agreed that it wouldn't be good to make a complete change on a 3. release candidate (this will be something for 1.1 :) ) I don't see a problem for a larger initial ramdisk, but this is more Jacques "area" ;) I will be away for a vacation also, so please excuse If you don't get an immediate answer. Greetings Eric Wolzak member of the Bering team > Hi Kim > > On Mon, Jun 24, 2002 at 03:05:38PM +0200, [EMAIL PROTECTED] said: > > Aanhalen Simon Blake <[EMAIL PROTECTED]>: > > > > > > > > Really? It worked for me - the packages out the far end were perfectly > > > backupable. I fail to see what temporary name you give your image > > > while > > > you populate it important - what is crucial is that at the end of the > > > process, the image must be gzipped, and called initrd.lrp. How you get > > > to that stage is up to you. > > > > Was this on a RC3 or a RC2 machine? > > If it was on RC3 can somebody of the bering crew confirm that > > something changed in the backupscript the fix the problem I had > > with backing up under RC2. > > Both - but in both cases you have to tell lrcfg.back.initrd the size of > the initrd to make - ie increase INITRD_SIZE from 1500 to 2000. I've > amended the recipe to specifically point that out, but as long as you do > that, both RC2 and RC3 work fine. Judging by the timestamps, I don't > think anything about the backup scripts has changed between RC2 and RC3 > > > I am not really getting an error I get a package that is too small to be right. > > If I reboot I get a kernel panick attempt to kill init. > > And yes I do rename the package to initrd.lrp > > How much to small? 600Kb, rather than 650Kb? If that's the case, it > sounds like you need to increase INITRD_SIZE as above. Bering team, is > there any reason the default ramdisk size can't be 2MB? I don't think > it would make more than a few bytes difference to the size on disk. > > Cheers > Si > ------------------------------------------------------- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel