Re: inital install & fdisk
Stephen Zander wrote:
>
>
> Eric Delaunay <delaunay@lix.polytechnique.fr> writes:
> > Even if the msdos fs is compiled into the kernel, the installation will fail
> > because resc1440.bin have to be mounted through the loop service and this one
> > fails if the image to mount is on nfs partition.
>
> Oh, joy... Well, I'm past that point anyway (wonderful what just ignoring
> a problem can do :))
>
> Clearly, though, the basic install process for debian/sparc has some flaws.
> Does someone own this process, are we waiting for the new bootdisks Bruce
> and others were building, or am I about to volunteer to fix things... :)
>
> BTW, why is there no kernel-image package for debina/sparc?
Well, I'm working on a kernel-image package based on 2.0.33.
I've just one packaged but I need to fix the postinst script (from
kernel-package 3.53) to support SILO instead of LILO.
I'm also working on new bootdisks but some packages/files are missing.
Especially there is no fdisk. Anyone want to package fdisk for sparc ?
(consider getting fdisk-2.5-1.src.rpm from RedHat).
Yesterday I packaged ash, cpio & util-linux Some of them were already
uploaded.
The following packages also need to move to libc6 before making bootdisks:
dpkg
procps
getty
perl
silo
I've worked on procps but I cannot release it before making binutils to work.
I'm succeeded in compiling binutils 2.8.1.0.19 but shared library name is
somewhat non conventional:
libbfd-2.8.1.0.19.so.0.0.0 with SONAME libbfd-2.8.1.0.19.so.0
instead of libbfd.so.2.8.1.0.19 I hoped to see.
Some of us have worked on perl with partial success. It don't pass all the
tests from the test suite and cannot load perl modules without LD_BIND_NOW env
variable set to 1 :-(
Bye.
--
Eric Delaunay | "La guerre justifie l'existence des militaires.
delaunay@lix.polytechnique.fr | En les supprimant." Henri Jeanson (1900-1970)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-sparc-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: