Re: 2.4 kernel as default boot kernel on CD #1 ??

2002-04-05 Thread Philip Blundell

On Fri, 2002-04-05 at 19:45, Jim Westveer wrote:
 Before you lam-bast me with a nastygram, please grab
 or create a copy of the woody CD's, and try an installation with 
 CD#1 as the disk you innitially boot from,  then try the
 CD#3 with the bf24 kernel.   The first thing you will notice
 is that the bf24 flavor first asks you for your language, where
 the default does not.

A more conservative way to get the language chooser going would be to
put compact or idepci on the first disk.  It doesn't require 2.4 as
such.

p.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Needs feedback and testing

2002-03-31 Thread Philip Blundell

On Sun, 2002-03-31 at 13:45, Raphael Hertzog wrote:
 Le Sun, Mar 31, 2002 at 12:47:55PM +0200, Petter Reinholdtsen crivait:
  Checking my freshly built CD, I see the following 21 language codes in
  .lp/:
  
ca cs da de en eo es fi fr gl hr hu it ja ko pl pt ru sk sv tr
  
  The install menu showed these language options.
  
ca cs da de en eo es gl hr hu it ja ko Cho?
  
  (I got someone else to test it.  I'm not sure what the Cho was. :-)
  
  Obviously someone is missing. :-)
 
 Well, AFAIK, the boot floppies directly include only a few (5-6)
 languages ... so something may be working if you get that much
 languages. I can't explain why the other disappeared however.

For a language to show up in the menu it needs to have a definition file
in dbootstrap/langs.  I know that this is the problem with Finnish (see
debian-i18n).  The disappearance of French and so on is a bit of a
mystery though.

p.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Bug#123948: can someone test the patch?

2002-03-02 Thread Philip Blundell

Who creates the existing .disk/info file?  I thought that was
debian-cd.  The new files Eduard is talking about can be done in exactly
the same way, as far as I can tell.

p.

On Sat, 2002-03-02 at 02:23, David Kimdon wrote:
 One things that came up in the BTS is that the debian-cd package
 currently doesn't need to manipulate the *.bin images that
 boot-floppies makes for it.  If I understand correctly what we are
 discussing here the debian-cd package will need to 'mount -o loop'
 during the build to add those files.  That will have to be done as
 root.  At one point we were trying to avoid that.
 
 FWIW,
 
 -David
 
 Fri, Mar 01, 2002 at 04:08:21PM + wrote:
  On Fri, 2002-03-01 at 13:09, Eduard Bloch wrote:
   A good compromise. I suggest two kinds of flags on the CD-ROM:
   
   .disk/kernel_installable
   .disk/base_installable
   
   The first marks the disk containing kernel and modules, the second the
   one with the basedebs.
  
  Sounds fine to me.
  
  p.
  
  
  
  -- 
  To UNSUBSCRIBE, email to [EMAIL PROTECTED]
  with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
  
  
 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: bug: cdimage.debian.org should warn against downloading with an ISDN connection

2001-11-25 Thread Philip Blundell

In message [EMAIL PROTECTED], Karl M. Hegbloom wr
ites:
 Perhaps if they do not, they should.  Someone should perform that
 labor and make it possible.  I wonder if it would require an entire
 new flavor of images, or if it's only a matter of inserting the
 correct modules?  I know zilch about ISDN.

Internal ISDN cards need a pile of modules, plus some supporting user-space 
stuff.  I don't think there is any hope of adding this to the woody boot-floppies
at this stage in the game, but it should be possible to support it under
debian-installer if someone wants to do the work.

External TAs should be okay.  I don't know if we ship the modules you need to use
USB modems right now, but it should be easy to add them to the driver disks if
not.  Ethernet and serial versions ought to just work already.

p.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]