On Mon, 27 Dec 1999, Dan Browning said:
DB>Why not just create an installation program that compiles the RPMS at
DB>installation time? For example, RedHat provides a binary i386 disc for
DB>those who want a quick & easy install. But there could also be an
DB>installation option that lets you chose to compile every source package
DB>before installation for your target platform (386, 486, 586, 686, athlon,
DB>etc.) Of course, the installation would take much longer this way, as it
DB>compiles every source package. But it would seem like an elegant way to
DB>satisfy everyone's desire. I've thought of writing such an program but I
DB>don't have the time currently.
Yech... it'd take a week to do an install! :-)
DB>> -----Original Message-----
DB>> From: Gustav Schaffter [mailto:[EMAIL PROTECTED]]
DB>> Sent: Monday, December 27, 1999 6:05 AM
DB>> To: redhat-list (Mailing list)
DB>> Subject: 686 distro. [Was: What about Mandrake?]
DB>>
DB>>
DB>> Hi,
DB>>
DB>> I'd *love* to see a 686 compiled RH distro. It's not just Linux that
DB>> goes through the evolution. So does the hardware available in hardware
DB>> stores.
DB>>
DB>> In a way, I can understand that RedHat doesn't want to go this way,
DB>> because then they would also have to provide a 586 distro etc, etc. And
DB>> when would they be able to discontinue the 386 compiled distro? Etc.
DB>>
DB>> But I think it could be done as a distributed volonteer developer
DB>> project. As long as RedHat doesn't want to do it themself, I don't see
DB>> why they should (or could?) oppose to such a project. Maybe that RedHat
DB>> would like to participate, if it's run by volonteers?
DB>>
DB>> Of course, there need to be a project definition, organization,
DB>> objective and scope definition, plus a serious coordination effort to
DB>> fulfill the sake.
DB>>
DB>> Idea: Maybe(!!) the objective would be to always maintain a distro
DB>> optimized for the very latest available Intel platform?
DB>>
DB>> If someone organized a distributed project to do this I would like to
DB>> participate. (Does it already exist?) But, I wouldn't find time to
DB>> manage it. Not even to participate in project management. I'd be happy
DB>> to maintain the latest 686 rpms for a limited and well defined subset of
DB>> the necessary packages. Kinda 20 - 30 rpms. Maybe more. I would also be
DB>> happy to provide limited space on my ftp server. Maybe 10 - 20 MB, but
DB>> no more. I don't see why such an effort couldn't even bring us a 686
DB>> compiled .iso of the RH setup.
DB>>
DB>> As I already stated, it would require someone else to organize the
DB>> effort, though.
DB>>
DB>> I'm aware that many people run Linux on 'old' hardware. I fully respect
DB>> this need, which is somewhat proven by the fact that I intend to install
DB>> RH6.1 on a few 486's laying around (when I find the time for it) and I
DB>> agree that there should be a 386 compatible distro available. Still,
DB>> nobody(?) *buys* a 386 or 486 system today.
DB>>
DB>> Regards
DB>> Gustav
DB>>
DB>> --
DB>> pgp = Pretty Good Privacy.
DB>>
DB>> To get my public pgp key, send an e-mail to: [EMAIL PROTECTED]
DB>>
DB>> Visit my web site at http://www.schaffter.com
DB>>
DB>>
DB>> --
DB>> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
DB>> as the Subject.
DB>>
DB>>
DB>
DB>
DB>
--
Chuck Mead, CTO, MoonGroup Consulting, Inc. <http://moongroup.com>
Mail problems? Send "s-u-b-s-c-r-i-b-e mailhelp" (no quotes and no
hyphens) in the body of a message to [EMAIL PROTECTED]
Public key available at: wwwkeys.us.pgp.net
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
