On Sun, Jun 23, 2002 at 09:06:26PM +0200, Kim Oppalfens said:
> Hi,
> 
> I would like to suggest some small changes to the documenation about upgrading
> to libc2.2.
> 
> -     First of all we might as well start with rc3, there is no real difference 
> in the process except
>       for downloading another image to start from .
> 
> -     Secondly if we change the lines
>       dd if=/dev/zero of=initrd-new bs=1M count=2
>       to
>       dd if=/dev/zero of=initrd.lrp bs=1M count=2
> 
>       AND
>       /sbin/mkfs.minix initrd-new
>       to      
>       /sbin/mkfs.minix initrd.lrp
> 
> We will create an initrd.lrp package that can be backed up without a glitch.

No, it won't - there's a gzip process that has to be gone through in
between - you have to gzip initrd-new.img, and rename initrd-new.img.gz
to initrd.lrp.  There also some other little bugs in that document that
I've found - I'll update it for rc3 shortly.
 
> Another modification I would like to see is the output of an ls -l from the
> root/lib directory just before recompressing the root.lrp.
> To be able to verify if we have the correct files. (I backed up libcrypto 
> using the current docs which is 900 KB in size.)
> I compared with my old root to find out I didn't need it).

That's presuambly what the file size displays are for - if your new
root.lrp isn't the size you'd expect, then you can bail out and
investigate.
 
Cheers
Si

 
> Thats about it, everything works fine using this procedure.
> 
> Kim Oppalfens
> 
> 
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> 
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel


-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/

_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to