[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Powerpc netinst iso.



Sven,

You didn't ask for my opinion, but here it is anyway...

As a user, I think splitting netinst/businesscard into separate 2.4 and 2.6 isos is a wonderful idea. The fewer unneeded Megabytes I have to download and burn before I can get started installing the better! I usually know whether I'm going to want to do 2.6 or 2.4 before I start the download process. I think it's an excellent trade-off.

Would it allow the the d-i components on the 2.6 iso to use 2.6-specific features at installation time? Would this be useful?

Enjoy!

Rick


On Saturday, July 17, 2004, at 07:58 PM, Sven Luther wrote:

Hello manty,

The powerpc netinst iso does not contain any 2.6 kernels .debs, and as
thus, it fails to install a debian system using 2.6 kernel, since it
tries to install some 2.4 kernels and fails.

There are two solutions possible :

  1) simply add the 2.6 kernels packages + initrd-tools +
  module-init-tools + mkvmlinuz. This would mean around 30MB of space
  used i think. Advantage: it is easy and works. Disadvantage: it grows
  the netinst iso another 30MB, and joeyh thinks that is too much for a
  netinst iso.

  => Additionally, in this case i want to modify the build so that the
  2.6 kernels are the default ones, and the 2.4 kernels are the
  alternative ones, accessed via linux24.

  2) split the netinst/businesscard isos into 2.4 and 2.6. This means
  that the isos will shirnk in size, as we gain around 10-15MB of space
  for removing those kernels. We duplicate the need of isos also. Here
again the standard one will be the 2.6 kernel, and the 2.4 one will be
  marked with the additional 24 par in the name or something.

What do you think of it, can you comment on this ? On what is the cost
of both solutions from your point of view ?

Friendly,

Sven Luther


--
To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org




Reply to: