In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>> >d. Work with me to get sparc turned on in its architecture list,
>> > so sparc images can enter the archive.
>>=20
>> I think silo-installer is needed before we start bothering with any
>> automatic building.
>
>Well yeah, it's kind of pointless to get it building on the autobuilders
>before it can usefully install a system. However, it does seem like you
>could take care of d. in short order from where you are now. Note that
>the autobuilt stuff is only boot images, not full CDs, so the lack of a
>boot loader installer does not directly impact it.
What should I do for this?
The sparc netcfg udebs need to get into the debian archives. (The
sparc autobuilder is either not running or still trying to catch up.
I'd rate python a higher priority.) Should I sign and upload the
package I built?
>> My next goal is booting from a hand-built cdrom, seeing if I can start
>> walking through the d-i prompts. Looking at the contents of the
>> sparc-mini iso, this is much simplier than I thought.
It loads silo, starts the kernel, and starts loading the initrd. It
then switches fonts and scrolls error messages off of the screen.
Either there is a problem with my handbuilt cdrom, or the initrd
doesn't work.
I may try using a serial console so I can capture the errors. (The
most interesting ones scroll off the screen quickly.)
>> Obviously, no useful install can be done with no silo-installer.
>Is there something badly wrong with the one in CVS?
Ben Collins mentioned he was working on it. Maybe he did complete it
without mentioning it on the mailing lists.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
