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

[Erik Andersen]

On Sat Apr 06, 2002 at 08:10:16AM +0100, Philip Hands wrote:
> The ISOLINUX/MEMDISK thing mentioned earlier looks interesting.  Has
> anyone played with this?  Presumably we could use MEMDISK to select

I've used Isolinux.  It works for me.  Lets me select from
multiple kernels on CD, with no obnoxious 1.4M kernel size limit
(and no 1.44 MB or 2.88 MB size limit on the root image either).

 -Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



msg18324/pgp0.pgp
Description: PGP signature

Re: "Testing" base floppies 4.4.2002 don't work

[Anthony Towns]

On Fri, Apr 05, 2002 at 01:35:52PM -0800, Matt Kraai wrote:
> On Fri, Apr 05, 2002 at 06:31:55PM +0200, Lorenzo J. Lucchini wrote:
> >   The current testing base floppy images do not work with the install system. 
>Disks from 1 to 9 work, but then disk 10 is seen as disk 1, as well as all 
> > following disks, and disk 20 is seen as disk 2.
> What architecture are you using?  What is the md5sum of the
> 10th disk image?

He's using i386 presumably, since there aren't any floppy images of base for
other architectures.

As far as I can tell the floppy images are correct, but I can't see any reason
for floppy_merge to not be coping correctly. md5sums should be:

103560e946ea5318825f6f753bad87b8  base14-1.bin
0fd2d0119c6123af89aa2b5208510dee  base14-10.bin
3c999cab208357d41a3856c74d53b419  base14-20.bin

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

 ``BAM! Science triumphs again!'' 
-- http://www.angryflower.com/vegeta.gif



msg18323/pgp0.pgp
Description: PGP signature

Bug#141447: menu to select kernel modules messed up

[Harald Dunkel]

Package: boot-floppies
Version: 3.0.22

Hi folks,

I tried this image to install Woody on my PC:

http://people.debian.org/~dwhedon/bootbf2.4.iso

Lilo params:

linux video=vga16:off vga=1

to avoid the low-res fb device and to get 80x50 chars instead.

No serious problems until I entered the menu to select the kernel
modules. When I scrolled down the menu was messed up.

Graphics card is an NVidia G-Force 2 GTS.


Regards

Harri



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

Bug#140579: TFTP Testing

[Junichi Uekawa]

"Philip Dodd" <[EMAIL PROTECTED]> cum veritate scripsit:

> Ok, this much is true. However, my personal sticking points aside, if there
> is an 'official' way of doing things, why then is the install guide so thin
> on the ground on these matters?  If a bug should be filed against the
> install guide to improve it, i would gladly, because it is as near as
> useless for booting tftp and nfs root machines (on intel at least).  the
> simple question of getting etherboot, for example - there are others, to
> boot tftpboot.img is not even mentioned, and that does seem to be one of the
> main uses of tftp booting on intel, though perhaps I am mistaken.

Yes, it is rather thin.

I've used grub with network card support (needs a recompile, the 
maintainer refused to include binaries for network support in the
Debian package) to do tftp boots.

It requires a NFS root, i.e. a installer directory with
dbootstrap etc. mountable from somewhere.

For example, this is the grub command-line I used to boot up
a note PC to start up a shell:

kernel (nd)/boot/netboot init=/bin/sh root=/dev/nfs nfsroot=192.168.1.1:/,flags=
ro



regards,
junichi


-- 
[EMAIL PROTECTED] : Junichi Uekawa   http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4


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

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

[Philip Hands]

On Sat, 2002-04-06 at 06:22, Anthony Towns wrote:

> I'm not really sure what part of "_STOP IT_" is so difficult to
> understand, but please _STOP IT_. If you want to move the bf2.4 kernel
> images onto the CD#2 bootsector, that's fine. But the default kernel
> for woody, and hence the image that should be on CD#1, has always been
> and remains 2.2.

Absolutely right.

The closest I'd be willing to go towards making a change, would be some
form of kernel selection menu on the first CD, still with the vanilla
2.2 kernel as the default, but giving people the choice even if they
only get CD#1.

That would be conditional on some evidence being forthcomming that the
resulting CD would be bootable on at least as many machines as is
currently the case.  Can anyone provide that?

The ISOLINUX/MEMDISK thing mentioned earlier looks interesting.  Has
anyone played with this?  Presumably we could use MEMDISK to select
between boot floppies, with no changes required to the boot floppy
images, so would only change things by bumping a few packages off the
end of CD#1.

Cheers, Phil.
-- 
Say no to software patents!  http://petition.eurolinux.org/

|)|  Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/
|-|  HANDS.COM Ltd.http://www.uk.debian.org/
|(|  10 Onslow Gardens, South Woodford, London  E18 1NE  ENGLAND



signature.asc
Description: This is a digitally signed message part

Re: frame-buffer on vanilla? (was: Re: 2.4 kernel as default boot kernel on CD #1 ??)

[Herbert Xu]

On Fri, Apr 05, 2002 at 10:31:25PM -0800, David Kimdon wrote:
>
> the first CD.  Is enabling frame-buffer an option on the vanilla
> flavor?  (Herbert, I cc'd you to get your opinion on that, I don't

Enabling VGA16 as a module will be done in the next release.
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


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

frame-buffer on vanilla? (was: Re: 2.4 kernel as default boot kernel on CD #1 ??)

[David Kimdon]

Sat, Apr 06, 2002 at 05:17:57AM +0200 wrote:
> On Sat, Apr 06, 2002 at 04:06:19AM +0100, Philip Hands wrote:
> > > > > cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
> > > I got a second, any opposed?
> > After considering this, I'm opposed.
> > If the decision is that the default boot floppies for woody i386 are
> > 2.2 ones (that don't do languages properly), I don't see that it is
> > within the aegis of debian-cd to make a unilateral decision to
> > override that for the CDs.
> 
> Note that the proposal was to use idepci by default, not bf2.4. The only
> change (besides the ide patches, and maybe something else) is that
> idepci has language chooser enabled.

Another big change that I had not considered is vanilla has many more
drivers as modules than idepci.  Hardware such as sound cards are not
supported in idepci.  In my eyes that kills the idea, though I really
wanted to see the language chooser . . . all 18 languages . . .  on
the first CD.  Is enabling frame-buffer an option on the vanilla
flavor?  (Herbert, I cc'd you to get your opinion on that, I don't
know all that is involved.)

Thanks,

David


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

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

[Anthony Towns]

On Fri, Apr 05, 2002 at 10:45:21AM -0800, Jim Westveer wrote:
> On Friday 05 April 2002 01:00, Anthony Towns wrote:
> > GUYS, _STOP IT_.
> > NOW IS _NOT_ THE TIME TO MAKE CHANGES TO THE WAY THE INSTALL WORKS.
> I am not suggesting changing anything in how the install
> works, or anything to do with the boot floppys packages.

> [...] 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.

IOW, the install works different.

I'm not really sure what part of "_STOP IT_" is so difficult to
understand, but please _STOP IT_. If you want to move the bf2.4 kernel
images onto the CD#2 bootsector, that's fine. But the default kernel
for woody, and hence the image that should be on CD#1, has always been
and remains 2.2.

Changing fundamental things in the install process (like the kernel
used, the machines supported, or the way you get to choose languages)
is completely out of the question at this point.

Cheers,
aj (woody release manager)

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

 ``BAM! Science triumphs again!'' 
-- http://www.angryflower.com/vegeta.gif



msg18317/pgp0.pgp
Description: PGP signature

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

[Jordi Mallach]

On Sat, Apr 06, 2002 at 04:06:19AM +0100, Philip Hands wrote:
> > > > cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
> > I got a second, any opposed?
> After considering this, I'm opposed.
> If the decision is that the default boot floppies for woody i386 are
> 2.2 ones (that don't do languages properly), I don't see that it is
> within the aegis of debian-cd to make a unilateral decision to
> override that for the CDs.

Note that the proposal was to use idepci by default, not bf2.4. The only
change (besides the ide patches, and maybe something else) is that
idepci has language chooser enabled.

-- 
Jordi Mallach Pérez || [EMAIL PROTECTED] || Rediscovering Freedom,
   aka Oskuro in|| [EMAIL PROTECTED]  || Using Debian GNU/Linux
 Reinos de Leyenda  || [EMAIL PROTECTED]  || http://debian.org

http://sindominio.net  GnuPG public information:  pub  1024D/917A225E 
telnet pusa.uv.es 23   73ED 4244 FD43 5886 20AC  2644 2584 94BA 917A 225E



msg18315/pgp0.pgp
Description: PGP signature

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

[Philip Hands]

On Sat, 2002-04-06 at 02:40, David Kimdon wrote: 
> Fri, Apr 05, 2002 at 05:00:45PM -0800 wrote:
> > > cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
> >   
> >   SCSI???  is there such a devil ?
> >   Its not in bf 3.0.22-2002-04-03  ;-/
> s/scsi/compact/
> 
> I got a second, any opposed?

After considering this, I'm opposed.

I don't see it as our job to override the decisions of other parts of
the project (excepting when not to do so would result in unusable CD
images).

If the decision is that the default boot floppies for woody i386 are
2.2 ones (that don't do languages properly), I don't see that it is
within the aegis of debian-cd to make a unilateral decision to
override that for the CDs.

CDs that don't use the default boot floppies by default (and I think we
all know that means on cd1) don't deserve the "Official" moniker, in
the same way that CDs that include my favourite five packages from
unstable don't deserve it.

We should aim for there to be as few suprises as possible, when moving
between CD installs, and the other ways of installing Debian.

Now, if you were to argue that bf2.4 should be the default floppies
for woody, that's a different thing, which I would probably agree with
if it had been decided a few months ago, but I think we're too late to
be changing that sort of thing now, unfortunately.

I'd also be pretty cheerful about making two netinst versions
available, one with bf2.4 on it, say, but if bf2.4 is being described
as "experimental" in the distribution, that's how we should label it
for the CDs too.

I know it's depressing to release things that are effectively out of
date, but we have to stop adding features at some point or we'll never
release.

Maybe we can use this as an incentive to make sure that it's not 18
months to the next release after woody. ;-)

Cheers, Phil
-- 
Say no to software patents!  http://petition.eurolinux.org/

|)|  Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/
|-|  HANDS.COM Ltd.http://www.uk.debian.org/
|(|  10 Onslow Gardens, South Woodford, London  E18 1NE  ENGLAND



signature.asc
Description: This is a digitally signed message part

cvs commit to boot-floppies/documentation/ca by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/documentation/ca
who:jordi
time:   Fri Apr  5 18:19:31 PST 2002
Log Message:
  Typo
  

Files:
changed:appendix.sgml


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

cvs commit to boot-floppies/documentation/en by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/documentation/en
who:jordi
time:   Fri Apr  5 18:19:31 PST 2002
Log Message:
  Typo
  

Files:
changed:appendix.sgml


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

Bug#140579: TFTP Testing

[Chris Tillman]

On Fri, Apr 05, 2002 at 04:19:08PM +0200, Philip Dodd wrote:
> > CC'ing the bug in question is the best way in all cases.  This lets us
> > follow the progress of the issue.
> 
> Ok i've taken note :)

...

> Ok, this much is true. However, my personal sticking points aside, if there
> is an 'official' way of doing things, why then is the install guide so thin
> on the ground on these matters?  If a bug should be filed against the
> install guide to improve it, i would gladly, because it is as near as
> useless for booting tftp and nfs root machines (on intel at least).  the
> simple question of getting etherboot, for example - there are others, to
> boot tftpboot.img is not even mentioned, and that does seem to be one of the
> main uses of tftp booting on intel, though perhaps I am mistaken.

I'd be happy to add stuff to the manual. You don't have to put
together a formal patch if you don't have time or don't like sgml,
just write up a decent addition / change and tell me which section it
should go in, keeping in mind neither I ( nor the reader) know what
the devil yo'ure talking about.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**




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

cvs commit to boot-floppies/debian by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/debian
who:jordi
time:   Fri Apr  5 18:16:32 PST 2002
Log Message:
  Bring Catalan docs up to date.
  

Files:
changed:changelog


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

cvs commit to boot-floppies/documentation/ca by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/documentation/ca
who:jordi
time:   Fri Apr  5 18:16:32 PST 2002
Log Message:
  Bring Catalan docs up to date.
  

Files:
changed:appendix.sgml boot-new.sgml inst-methods.sgml partitioning.sgml 
rescue-boot.sgml


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

cvs commit to boot-floppies/documentation by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/documentation
who:jordi
time:   Fri Apr  5 18:16:32 PST 2002
Log Message:
  Bring Catalan docs up to date.
  

Files:
changed:release-notes.ca.sgml


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

cvs commit to boot-floppies/documentation by jordi

[Debian Boot CVS Master]

Repository: boot-floppies/documentation
who:jordi
time:   Fri Apr  5 18:03:33 PST 2002
Log Message:
  Typo
  

Files:
changed:release-notes.sgml


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

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

[David Kimdon]

Fri, Apr 05, 2002 at 05:00:45PM -0800 wrote:
> > cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
>   
>   SCSI???  is there such a devil ?
>   Its not in bf 3.0.22-2002-04-03  ;-/
s/scsi/compact/

I got a second, any opposed?

-David


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

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

[Jim Westveer]

-BEGIN PGP SIGNED MESSAGE-
Hash: MD5

On Friday 05 April 2002 16:50, David Kimdon wrote:
> Fri, Apr 05, 2002 at 07:59:05PM +0100 wrote:
> > On Fri, 2002-04-05 at 19:45, Jim Westveer wrote:

>
> aph and I were just talking on irc, how about :
>
> cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
  
  SCSI???  is there such a devil ?
  Its not in bf 3.0.22-2002-04-03  ;-/
- -- 

Ciao,

- --
Jim Westveer 
- 
I wish there was a button on my monitor for intelligence.  
There's a button called `brightness', but it doesn't work.
- 
E-Mail: [EMAIL PROTECTED]  [EMAIL PROTECTED]
work :  425-591-3002  KC7JYJ 
pgp-key 0x36129171gpg-key 0x9823336C  
- 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEAREBAAYFAjyuSMoACgkQXpzfopgjM2zStwCdGOKys6wpMGUouSa9kmw3aGmv
Nn0AnR6zMV2kx0XdDe++RB6LDQ7p5VTe
=DqMa
-END PGP SIGNATURE-


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

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

[John H. Robinson, IV]

On Fri, Apr 05, 2002 at 04:50:50PM -0800, David Kimdon wrote:
> 
> cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla
> 
> Any seconds?

seconded.

-john


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

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

[David Kimdon]

Fri, Apr 05, 2002 at 07:59:05PM +0100 wrote:
> 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.

aph and I were just talking on irc, how about :

cd1: idepci; cd2 scsi; cd3: bf2.4; cd4: vanilla

That gives us language chooser on the first CD, a big plus, while
still giving us 2.2 as 'default'.  IMO leaving the language chooser
off the first CD would be a real shame.

Any seconds?

-David


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

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

[Thomas Poindessous]

Le ven 05/04/2002 à 21:25, Chris Lawrence a écrit :
> > 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.
> 
> It'd be nice to be able to add something like
> http://www.nu2.nu/diskemu/; however, it's not source-available, so it
> probably doesn't belong on official CDs.
> 
> Another possibility might be HPA's isolinux tool, based on syslinux:
> http://syslinux.zytor.com/iso.php with or without MEMDISK
> http://syslinux.zytor.com/memdisk.php; basically, instead of putting
> the rescue disk in the boot sector, you put the isolinux image there,
> and have a menu to choose between kernels to load.

For next release (post woody), you might consider using grub + cd_boot
patches. It work quite nicely. You've got a boot cd with a grub menu.

-- 
Thomas Poindessous
[EMAIL PROTECTED]


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

cvs commit to boot-floppies/utilities/dbootstrap/po by peterk

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   lör apr  6 00:16:09 CEST 2002
Log Message:
  s/GTP/GPT/

Files:
changed:sv.po


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

Processed: close 138369

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> close 138369
Bug#138369: boot-floppies: incorrect keystroke (alt-F4) for debug info given.
Bug closed, send any further explanations to Scott Eisert <[EMAIL PROTECTED]>

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Re: "Testing" base floppies 4.4.2002 don't work

[Matt Kraai]

On Fri, Apr 05, 2002 at 06:31:55PM +0200, Lorenzo J. Lucchini wrote:
>   The current testing base floppy images do not work with the install system. Disks 
>from 1 to 9 work, but then disk 10 is seen as disk 1, as well as all 
> following disks, and disk 20 is seen as disk 2.

What architecture are you using?  What is the md5sum of the
10th disk image?

Matt


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

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

[Ben Collins]

Please take me of the Cc of this thread.

-- 
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/


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

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

[Eduard Bloch]

#include 
Anthony Towns wrote on Fri Apr 05, 2002 um 07:00:08PM:
> On Fri, Apr 05, 2002 at 10:07:38AM +0200, Eduard Bloch wrote:
> > #include 
> > Jim Westveer wrote on Thu Apr 04, 2002 um 05:24:24PM:
> > > > And last, woody ought to be 2.2 based and not 2.4 based ... but since I
> > > > also find it lame to use 2.2.x by default nowadays ...
> > > I disagree,  2.4.x kernels have been out for over 2 years.we should
> > > not release a "new" version of Debian with such an outdated kernel !
> > > [appologies in advance to the boot-floppy group for all their hard work]
> > Agreed. The decission, which flavor has to be on the first CD, is done
> > by debian-cd's scripts, see
> > /usr/share/debian-cd/tools/boot/woody/boot-i386. CD distributors can
> > change it if they like.
> 
> GUYS, _STOP IT_.
> 
> NOW IS _NOT_ THE TIME TO MAKE CHANGES TO THE WAY THE INSTALL WORKS.
> 
> 2.4 is not the default kernel for woody installs, 2.2 is. Yes, it sucks,

What is _default_? What is _option_? Saying that something is default
implies that you stick to this thing from the installation time until
you install another (optional) thing manually. This is not the case
here. You can completely install and work with bf2.4 unless you decide
to change to optimised 2.4.x kernels or 2.2.x.

> and I don't care. If anyone asks why, blame me. DO NOT MAKE FURTHER
> CHANGES TO THE WAY DEFAULT INSTALLS WORK. Not if it makes a billion more
> people able to use Debian. Not if it's so fundamentally offensive that
> it makes you want to disembowel yourself with a screwdriver.

The problem is, many people download only the first CD and install the
rest from the net. Or they even do not look on other CDs, boot with the
first one and are disappointed (no lang chooser, missing drivers for
various hardware, harddisk controllers, USB keyboards, etc. etc.).

This is not a technical change. It is a political one. debian-cd still
needs at least one release before Woody. IMHO enough time to change.

> debian-cd has exactly one goal right now: make sure we're ready to produce
> official CDs that include the entire archive and let you get started on
> an install.

As said before, I know enough people that run their harddisks on Promise
or Highpoint controllers. With the vanilla flavor, Debian would be
completely useless for them.

Gruss/Regards,
Eduard.
-- 
Ich glaube nicht, daß man dieses Stück in Software umgesetzte Scheiße über-
haupt mieser machen kann, als es sowieso schon ist. Das dürfte das einzige
Programm sein, das vom Verhalten und seinen Anwendern her schlimmer als XP
auf einem Amiga ist. - Manuel Richardt in ka.talk ueber Outlook Express



msg18300/pgp0.pgp
Description: PGP signature

cvs commit to boot-floppies/utilities/dbootstrap/po by peterk

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   fre apr  5 22:46:59 CEST 2002
Log Message:
  Updated to latest strings.

Files:
changed:sv.po


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

cvs commit to boot-floppies/utilities/dbootstrap/po by peterk

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   fre apr  5 22:39:36 CEST 2002
Log Message:
  Completed

Files:
changed:sv.po


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

cvs commit to boot-floppies/utilities/dbootstrap/po by peterk

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   fre apr  5 22:18:57 CEST 2002
Log Message:
  Applied patch from André Dahlqvist <[EMAIL PROTECTED]>

Files:
changed:sv.po


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

boot logo

[Eduard Bloch]

This is not for the default installation CDs, but may interesst CD
distributors. With this patch you can install own logos. Requires
instlogo.bmp, format is described in lilo.conf(5).

Gruss/Regards,
Eduard.
-- 
> [Microsoft wirbt:] "Ein offenes Betriebssystem kann schon mal mutieren."
Mutieren tun vor allem MS-proprietäre Dateiformate.


Index: i386-specials/mini-iso.sh
===
RCS file: /cvs/debian-boot/boot-floppies/i386-specials/mini-iso.sh,v
retrieving revision 1.8
diff -u -r1.8 mini-iso.sh
--- i386-specials/mini-iso.sh   2002/04/01 15:38:52 1.8
+++ i386-specials/mini-iso.sh   2002/04/05 12:54:06
@@ -82,6 +82,10 @@
touch ${CD}/.disk/base_installable
 fi
 
+if [ -e instlogo.bmp ] ; then
+   cp instlogo.bmp $CD
+fi
+
 if [ "x${flavour}" != "x" ]; then
   ln -s ../../../../../../../boot/rescue.bin ${BF}/images-1.44/${flavour}/rescue.bin
 else
Index: utilities/dbootstrap/bootconfig.c
===
RCS file: /cvs/debian-boot/boot-floppies/utilities/dbootstrap/bootconfig.c,v
retrieving revision 1.194
diff -u -r1.194 bootconfig.c
--- utilities/dbootstrap/bootconfig.c   2002/03/25 05:58:20 1.194
+++ utilities/dbootstrap/bootconfig.c   2002/04/05 12:54:08
@@ -1886,8 +1886,9 @@
 "# You have the choice between: bmp, compat, menu and text\n" \
 "# Look in /boot/ and in lilo.conf(5) manpage for details\n" \
 "#\n" \
-"install=/boot/boot-menu.b\n" \
+"install=/boot/boot-%s.b\n" \
 "\n" \
+"%s\n" \
 "# Specifies the location of the map file\n" \
 "#\n" \
 "map=/boot/map\n" \
@@ -2265,7 +2266,7 @@
 static int run_lilo(char *boot, int fixmap, struct d_choices *others, int o_number)
 {
   FILE* filep;
-  int status = 0, i=0;
+  int status = 0, i=0, bmp=0;
 #ifndef _TESTING_
   struct stat statbuf;
   char * devnumber;
@@ -2288,6 +2289,8 @@
   pleaseWaitBox(_("Running LILO to make the kernel able to boot "
  "from the hard disk without a boot floppy..."));
 
+  bmp = (! system("test -f /target/boot/instlogo.bmp"));
+
   if ((filep = fopen(BC_LILO_CONF, "w")) == NULL) {
 boxPopWindow();
 #ifdef _TESTING_
@@ -2324,15 +2327,15 @@
   if(o_number > 0) 
  prompt = "prompt\ntimeout=150\n";
   else 
- prompt = "";
+ prompt = "prompt\ntimeout=150\n";
 
   if (append_opts && strlen (append_opts)) {
   append = (char *)malloc (strlen (append_opts) + 1 + 10); /* "append=\"" + 
"\"\n"*/
   sprintf (append, "append=\"%s\"\n", append_opts);
-  fprintf(filep, BC_LILOTEMPLATE1, boot_map, bootpart_map, boot, Root->name, 
prompt, append);
+  fprintf(filep, BC_LILOTEMPLATE1, boot_map, bootpart_map, boot, Root->name, bmp 
+? "bmp" : "menu", bmp ? "bitmap=/boot/instlogo.bmp\n" : "" , prompt, append);
   free (append);
   } else {
-  fprintf(filep, BC_LILOTEMPLATE1, boot_map, bootpart_map, boot, Root->name, 
prompt, "");
+  fprintf(filep, BC_LILOTEMPLATE1, boot_map, bootpart_map, boot, Root->name, bmp 
+? "bmp" : "menu", bmp ? "bitmap=/boot/instlogo.bmp\n" : "" , prompt, "");
   }
 #ifndef _TESTING_
   if ( NAME_ISDIR(MOD_SAVE_DIR,&statbuf) )
@@ -2638,7 +2641,21 @@
case 0:
   break;
case 1:
-  menuBox(_("Following partitions are bootable: "), _("Other bootable 
partitions"), bootable, boot_number, 1);
+  { 
+ char * buf;
+ int i;
+ buf = (char *) calloc (boot_number, 50);
+ for(i=0; i< boot_number; i++) {
+strcat(buf, "\t");
+strcat(buf, bootable[i].tag);
+strcat(buf, "(");
+strcat(buf, bootable[i].string);
+strcat(buf, ")\n");
+ }
+ sprintf(prtbuf, _("The following partitions seem to be bootable and 
+would be added to the boot menu:\n\n%s"), buf);
+ problemBox(prtbuf, _("Other bootable partitions"));
+ free(buf);
+  }
   goto redisplay_options;
case 2:
   boot_number=0;
Index: utilities/dbootstrap/extract_base.c
===
RCS file: /cvs/debian-boot/boot-floppies/utilities/dbootstrap/extract_base.c,v
retrieving revision 1.79
diff -u -r1.79 extract_base.c
--- utilities/dbootstrap/extract_base.c 2002/04/05 08:12:08 1.79
+++ utilities/dbootstrap/extract_base.c 2002/04/05 12:54:09
@@ -32,6 +32,7 @@
   chdir("/target");
   sprintf(prtbuf,"tar -xf %s",fil);
   status=execlog(prtbuf, LOG_INFO);
+  execlog("mkdir /target/boot; cp /instmnt/instlogo.bmp /target/boot/", LOG_INFO);
   chdir("/");
   boxPopWindow();
   if (status) {

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

[Chris Lawrence]

On Apr 05, Philip Blundell wrote:
> 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.

It'd be nice to be able to add something like
http://www.nu2.nu/diskemu/; however, it's not source-available, so it
probably doesn't belong on official CDs.

Another possibility might be HPA's isolinux tool, based on syslinux:
http://syslinux.zytor.com/iso.php with or without MEMDISK
http://syslinux.zytor.com/memdisk.php; basically, instead of putting
the rescue disk in the boot sector, you put the isolinux image there,
and have a menu to choose between kernels to load.


Chris
-- 
Chris Lawrence <[EMAIL PROTECTED]> - http://www.lordsutch.com/chris/

Computer Systems Manager, Physics and Astronomy, Univ. of Mississippi
125B Lewis Hall - 662-915-5765


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

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

[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]

cvs commit to boot-floppies by pb

[Debian Boot CVS Master]

Repository: boot-floppies
who:pb
time:   Fri Apr  5 10:47:55 PST 2002
Log Message:
  arm: remove unwanted kernels
  
  

Files:
changed:release.sh


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

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

[Jim Westveer]

-BEGIN PGP SIGNED MESSAGE-
Hash: MD5

On Friday 05 April 2002 01:00, Anthony Towns wrote:
> On Fri, Apr 05, 2002 at 10:07:38AM +0200, Eduard Bloch wrote:
> > #include 
> >

>
> GUYS, _STOP IT_.
>
> NOW IS _NOT_ THE TIME TO MAKE CHANGES TO THE WAY THE INSTALL WORKS.
>


aj,

I do not want to raise the voice of the woody release manager, 
but, please just hear me out for a moment.

I am not suggesting changing anything in how the install
works, or anything to do with the boot floppys packages.

Currently, debian-cd creates ISO images that are spread
accross several volumes.  A while back we decided to put
different flavors of the i386 boot-floppy kernels on each of the
CD's, to make it easier for someone to use those flavors.

I setup the script to put one flavor on the first disk, another
on the second, and so on and so on.  Currently the debian-cd
scripts are setup to put the boot-floppys "default" kernel on the
first cd,  the "compact" flavor on the second CD, the bf24 flavor
on the third CD, the "idepci" flavor on the fourth CD, and all
subsiquent CD's have the "default" flavor.

What I have suggested is simply swaping positions of the
kernel images of the first and third CD.  I am not suggesting
the change of any other software, or in any way the mannor
in which the disks are created.

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.  Additionally I beleive you will
find that the bf24 actually works better on newer hardware.

Thanks for your consideration.

- -- 



- --
Jim Westveer 
- 
I like the word pedantic.  
But I like the word revolutionary better.
- 
E-Mail: [EMAIL PROTECTED]  [EMAIL PROTECTED]
work :  425-591-3002  KC7JYJ 
pgp-key 0x36129171gpg-key 0x9823336C  
- 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEAREBAAYFAjyt8NEACgkQXpzfopgjM2wrRQCcD2BIQDOJ8Da9wuLIsU31wcgz
Hv4AnjTPPFhzx7km6KdyShODQYjZddnO
=im3f
-END PGP SIGNATURE-


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

cvs commit to boot-floppies/debian by pb

[Debian Boot CVS Master]

Repository: boot-floppies/debian
who:pb
time:   Fri Apr  5 10:47:21 PST 2002
Log Message:
  log changes
  
  

Files:
changed:changelog


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

cvs commit to boot-floppies/utilities/dbootstrap by pb

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap
who:pb
time:   Fri Apr  5 10:30:24 PST 2002
Log Message:
  Fudge keyboard name prefix back to "i386" when installing on RiscPC.
  If this is not done, console-common attempts to translate the keycodes
  twice, yielding a totally unusable keymap.
  
  

Files:
changed:kbdconfig.c


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

Re: Debian GNU/Linux on a floppyless Alpha

[Falk Hueffner]

Frank Ecke <[EMAIL PROTECTED]> writes:

> I've had some fun trying to install the Potato release
> of Debian GNU/Linux on a DEC Alpha Station.  Everything
> was fine until the installation routine asked me to
> place a floppy disk into the drive associated with
> /dev/fd0.  Apparently, it was about to create a "rescue
> floppy."
> 
>I didn't want to do that but had no option to skip
> that step.  What's even worse, even if I had wanted to
> create such a floppy, I would have been unable to do
> so.  This jewel of an Alpha doesn't have a floppy disk
> drive, yet the installation routine was convinced of the
> contrary!
> 
>The favor I'd like to ask of you now is: Could you
> modify the installation routine so that those of us who
> don't want a "rescue floppy" or don't have a floppy
> drive can get by?

The current version of the boot floppies doesn't even generate a
rescue floppy by default, and I was pretty sure the potato version did
the same... are you sure it didn't ask for the drivers disk or
something? Also it would be helpful to know what firmware you were
using and how you booted the machine (tftp?).

In any case, the potato boot floppies are unmaintained, and you should
probably rather try the pre-release woody boot floppies. If that still
doesn't work, please file a bug report.

Falk


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

Debian GNU/Linux on a floppyless Alpha

[Frank Ecke]

Dear Debian folks,

I've had some fun trying to install the Potato release
of Debian GNU/Linux on a DEC Alpha Station.  Everything
was fine until the installation routine asked me to
place a floppy disk into the drive associated with
/dev/fd0.  Apparently, it was about to create a "rescue
floppy."

   I didn't want to do that but had no option to skip
that step.  What's even worse, even if I had wanted to
create such a floppy, I would have been unable to do
so.  This jewel of an Alpha doesn't have a floppy disk
drive, yet the installation routine was convinced of the
contrary!

   The favor I'd like to ask of you now is: Could you
modify the installation routine so that those of us who
don't want a "rescue floppy" or don't have a floppy
drive can get by?


Regards,

Frank

--

Frank Ecke <[EMAIL PROTECTED]>

Paranoid schizophrenics outnumber their enemies at least
two to one.


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

boot-floppies_3.0.22_arm.changes ACCEPTED

[Debian Installer]

Accepted:
install-doc_3.0.22_arm.deb
  to pool/main/b/boot-floppies/install-doc_3.0.22_arm.deb


Thank you for your contribution to Debian.


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

boot-floppies_3.0.22_mipsel.changes ACCEPTED

[Debian Installer]

Accepted:
install-doc_3.0.22_mipsel.deb
  to pool/main/b/boot-floppies/install-doc_3.0.22_mipsel.deb


Thank you for your contribution to Debian.


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

boot-floppies_3.0.22_mips.changes ACCEPTED

[Debian Installer]

Accepted:
install-doc_3.0.22_mips.deb
  to pool/main/b/boot-floppies/install-doc_3.0.22_mips.deb


Thank you for your contribution to Debian.


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

"Testing" base floppies 4.4.2002 don't work

[Lorenzo J . Lucchini]

Hello,
  The current testing base floppy images do not work with the install system. Disks 
from 1 to 9 work, but then disk 10 is seen as disk 1, as well as all 
following disks, and disk 20 is seen as disk 2.

Thank You for Your time

by LjL
  [EMAIL PROTECTED]



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

Bug#141166: boot-floppies: Network configuration should not use "auto" for PCMCIA network cards

[Matt Kraai]

On Fri, Apr 05, 2002 at 11:25:35AM -0500, Brian Mays wrote:
> As you can see below, we're trying to resolve any potential issues that
> might be messing up the installation procedure.  Can you provide the
> information requested below?  That is, could you check the version of
> the pcmcia-modules packages on your system?  You should be able to get
> this information using the following commands:
> 
> ls -d /usr/share/doc/pcmcia-modules*
> gzip -dc /usr/share/doc/pcmcia-modules*/changelog.Debian.gz | head -1

It would also be helpful to know which drivers were missing.

Matt


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

Bug#141166: boot-floppies: Network configuration should not use "auto" for PCMCIA network cards

[Brian Mays]

Patrik,

As you can see below, we're trying to resolve any potential issues that
might be messing up the installation procedure.  Can you provide the
information requested below?  That is, could you check the version of
the pcmcia-modules packages on your system?  You should be able to get
this information using the following commands:

ls -d /usr/share/doc/pcmcia-modules*
gzip -dc /usr/share/doc/pcmcia-modules*/changelog.Debian.gz | head -1

Thanks,

- Brian

--- Forwarded Message

To: Brian Mays <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#141166: boot-floppies: Network configuration should not use "auto" 
for PCMCIA network cards
Sender: Matt Kraai <[EMAIL PROTECTED]>

On Fri, Apr 05, 2002 at 06:10:27AM -0500, Brian Mays wrote:
> Here is the information that I was able to get from the user:
> 
> > > The interface xxx (xxx) seems to be a PCMCIA card. Is this
> > > correct?
> 
> > No, I wasn't asked that. However, I suspect that my case is pretty
> > hard to take into account in an installation script, at least with the
> > current way of handling network cards (my understanding of this is not
> > the best admittedly, I'm a programmer of very little brain).
> >
> > These were the steps I took to install the system on a new, empty hd
> > (after trying to get the boot floppies to work with a usb floppy):
> >
> > I made a small dos partition and shuttled over linux, drivers.tgz etc
> > to that partition via diskettes. Loaded the kernel drivers from the
> > dos partition.
> >
> > Next I installed the system via http by using the eepro card in the
> > port replicator (although it's not really a replicator since there are
> > no ports on the computer itself. But I digress). Sometime around this
> > point I was asked if I wanted to remove the pcmcia drivers, since I
> > wasn't using them, but I said no.
> >
> > The reason I used the eepro card (I don't normally use the replicator
> > since it's large and in the way, the only badly designed part of the
> > laptop) was that I couldn't get the wlan card to work with the boot
> > floppies, there wasn't a driver for the orinoco_cs card that I could
> > find and the wavelan driver didn't work (at least not immediatly, so I
> > just went with what worked).
> >
> > Once I had the base system installed I upgraded the kernel to 2.4.18,
> > as instructed by our sysadmin, and kompiled appropriate modules etc.
> >
> > Only after this did I start using the wlan and 3com pcmcia cards and
> > ran into the glitch I mailed to the list about.
> >
> > I hope this helps, and thanks again, I've got my setup working
> > smthly now.
> 
> It looks like this could be a non-issue, and the installation scripts
> are fine.  What do you think?

The boot-floppies don't prevent the user from borking their
installation after they have finished, nor should they.  :)

The lack of appropriate drivers sounds like a bug, however.
Could you find out which pcmcia-modules package was in use?

Matt

--- End of Forwarded Message



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

Bug#140980: boot-floppies: confusing message box

[David Kimdon]

Thu, Apr 04, 2002 at 01:29:30AM +0200 wrote:
> message, IMHO. Patch attached, untested.

Yes, that is exactly what I am looking for.   Obviously someone needs
to test it, but it fixes this bug.


Thanks,

David


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

esto te ayuda

[Natalia]

ENVIAMOS SU
PUBLICIDAD POR E MAIL

->Mas de 390 bases EXCLUSIVAS (por rubro, provincia, pais...)
->NOSOTROS hacemos el envio (no tenga problemas con su servidor)
->BUSQUEDAS de emails segun "palabra clave"
->Carga de SU PAGINA WEB en el Outlook del receptor
->Promociones especiales

$5 CADA 1000 MAILS ENVIADOS

INFORMESE UNICAMENTE AL (011) 15-4427-1044 (AGENDELO YA)
Lunes a domingo de 10 a 22 Hs.


para ser removido de esta lista responda el mail con REMOVE en asunto


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

Bug#141166: boot-floppies: Network configuration should not use "auto" for PCMCIA network cards

[Matt Kraai]

On Fri, Apr 05, 2002 at 06:10:27AM -0500, Brian Mays wrote:
> Here is the information that I was able to get from the user:
> 
> > > The interface xxx (xxx) seems to be a PCMCIA card. Is this
> > > correct?
> 
> > No, I wasn't asked that. However, I suspect that my case is pretty
> > hard to take into account in an installation script, at least with the
> > current way of handling network cards (my understanding of this is not
> > the best admittedly, I'm a programmer of very little brain).
> >
> > These were the steps I took to install the system on a new, empty hd
> > (after trying to get the boot floppies to work with a usb floppy):
> >
> > I made a small dos partition and shuttled over linux, drivers.tgz etc
> > to that partition via diskettes. Loaded the kernel drivers from the
> > dos partition.
> >
> > Next I installed the system via http by using the eepro card in the
> > port replicator (although it's not really a replicator since there are
> > no ports on the computer itself. But I digress). Sometime around this
> > point I was asked if I wanted to remove the pcmcia drivers, since I
> > wasn't using them, but I said no.
> >
> > The reason I used the eepro card (I don't normally use the replicator
> > since it's large and in the way, the only badly designed part of the
> > laptop) was that I couldn't get the wlan card to work with the boot
> > floppies, there wasn't a driver for the orinoco_cs card that I could
> > find and the wavelan driver didn't work (at least not immediatly, so I
> > just went with what worked).
> >
> > Once I had the base system installed I upgraded the kernel to 2.4.18,
> > as instructed by our sysadmin, and kompiled appropriate modules etc.
> >
> > Only after this did I start using the wlan and 3com pcmcia cards and
> > ran into the glitch I mailed to the list about.
> >
> > I hope this helps, and thanks again, I've got my setup working
> > smthly now.
> 
> It looks like this could be a non-issue, and the installation scripts
> are fine.  What do you think?

The boot-floppies don't prevent the user from borking their
installation after they have finished, nor should they.  :)

The lack of appropriate drivers sounds like a bug, however.
Could you find out which pcmcia-modules package was in use?

Matt


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

Bug#140579: TFTP Testing

[Philip Dodd]

> CC'ing the bug in question is the best way in all cases.  This lets us
> follow the progress of the issue.

Ok i've taken note :)

>
> > The tftpboot.img alone indeed seems not to include a root.bin image.
>
> No it does not.  That is by design, so I'm told.  Apparently there is
> no standard way to include the root image with the TFTP kernel image.
> Thus the root filesystem must be loaded and mounted by other means
> (root=/dev/nfs kernel boot argument, apparently).
>
> > I can make it boot by taking the bf2.4 root.bin and using mknbi-linux
>
> What is mknbi-linux?  Will that work with most/all i386 hardware that
> is even capable of netbooting?

It is a debian package that creates Net Boot Images, hence the name.  I
created an image using it to include the boot.bin as a ram disk and to
append root=/dev/ram as boot parameter to the tftpboot.img (also directly to
a home-made kernel bzImage with the root.bin)  Etherboot picks all this up
directly and fetches the image and boots straight into the install.

> >
> > i am trying to install onto an nfs / partition and this bit gives me
> > lots of trouble.  it complains about locking when trying to chroot
> > /target dpkg --force-depends --install etc.  i can get no further.  I
> > assume this is a seperate issue, but think that it needs solving for
> > tftp to be any use, since those using it may use it because the
> > machine is diskless.
>
> Well, it's purely an NFS and kernel issue at this point.  Perhaps you
> don't have lockd running on the server?  Have you consulted the docs,
> Debian and otherwise?  NetBSD has some pretty good instructions on
> this sort of stuff...

Yes, i guess so.  However, the machine in question runs as an NFS server for
all the machines on my local net, including linux and solaris 2.8 machines,
and _none_ of them complain about locking.  lockd is of course running on
the server - i did some basic checks, but will of course thoroughly inspect
my nfs setup before assuming this part is a bug.

>
> > i am also unable to ascertain the correct method of installing the
> > kernel and driver modules (the only success i have had is installing
> > the bf2.4 ones from /dev/fd0).
>
> Why not from the network?

good question. :)  would it change anything though?

>
> > The server (dhcp, nfs-kernel) is a linux debian woody.  i could test
> > this with solaris servers if it helps to take server side problems out
> > of the picutre, but i don't think the problem is here.
> >
> > The install guide is very unclear on both tftp booting and nfs root
> > installs.
> >
> > I am willing to help if i can, and to test various configs if
> > necessary, the client on which i'm installing is a test machine so
> > it's no prob.  I would also like to improve the install guide sections
> > once we've tracked down an appropriate method for tftp installs.
>
> Well, the fact is, you can't get it working, so I doubt you can help
> us much.

Ok, this much is true. However, my personal sticking points aside, if there
is an 'official' way of doing things, why then is the install guide so thin
on the ground on these matters?  If a bug should be filed against the
install guide to improve it, i would gladly, because it is as near as
useless for booting tftp and nfs root machines (on intel at least).  the
simple question of getting etherboot, for example - there are others, to
boot tftpboot.img is not even mentioned, and that does seem to be one of the
main uses of tftp booting on intel, though perhaps I am mistaken.

Cheers,

Philip DODD




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

Re: Security bug in latest iso image

[Eduard Bloch]

> firstly I'd like to say that I very much appreciate your work. I have 
> used your netinstall image for several times now at home and at work. 
> But since the most machines I installed were servers without any user 
> accounts on them, I haven't noticed that the /root directory after 
> installation has permission mode 0755 instead of 0750. I guess that some 
> deb is faulty. Concerned image is 3.0.22 from 22.03.2002.

AFAIK this is the default mode on Debian. I do not see how this should
affect the security - you should never work as root and check modes if
you store sensitive data.

Gruss/Regards,
Eduard.
-- 
 /"We are M$ of Borg. We will add your technology to our own crap. /
/Your company will be bought. Open Source is futile!" / 


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

Bug#141166: boot-floppies: Network configuration should not use "auto" for PCMCIA network cards

[Brian Mays]

Matt Kraai wrote:

> Umm, something is rotten in the state of Denmark...
> 
>   if (!has_pcmcia)
> fprintf(p_file, "auto %s\n", netinterface);
>   fprintf(p_file, "iface %s inet dhcp\n", netinterface);
> 
> ...so it must not have set has_pcmcia, which is supposed to be
> set...
> 
>   has_pcmcia = 0;
>   if (netinterface && NAME_ISDIR("/proc/bus/pccard", &nc_statbuf)) {
> snprintf(prtbuf, PRTBUFSIZE, _("The interface %s (%s) seems to be a PCMCIA card. 
>Is this correct?"), 
>  netinterface, get_ifdsc(netinterface));
> if (bootargs.isquiet || yesNoBox(prtbuf, _("Confirmation")) == DLG_YES) {
>   has_pcmcia = 1;
> }
>   }
> 
> Did it display this confirmation dialog?  Did /proc/bus/pccard
> exist?

Here is the information that I was able to get from the user:

> > The interface xxx (xxx) seems to be a PCMCIA card. Is this
> > correct?

> No, I wasn't asked that. However, I suspect that my case is pretty
> hard to take into account in an installation script, at least with the
> current way of handling network cards (my understanding of this is not
> the best admittedly, I'm a programmer of very little brain).
>
> These were the steps I took to install the system on a new, empty hd
> (after trying to get the boot floppies to work with a usb floppy):
>
> I made a small dos partition and shuttled over linux, drivers.tgz etc
> to that partition via diskettes. Loaded the kernel drivers from the
> dos partition.
>
> Next I installed the system via http by using the eepro card in the
> port replicator (although it's not really a replicator since there are
> no ports on the computer itself. But I digress). Sometime around this
> point I was asked if I wanted to remove the pcmcia drivers, since I
> wasn't using them, but I said no.
>
> The reason I used the eepro card (I don't normally use the replicator
> since it's large and in the way, the only badly designed part of the
> laptop) was that I couldn't get the wlan card to work with the boot
> floppies, there wasn't a driver for the orinoco_cs card that I could
> find and the wavelan driver didn't work (at least not immediatly, so I
> just went with what worked).
>
> Once I had the base system installed I upgraded the kernel to 2.4.18,
> as instructed by our sysadmin, and kompiled appropriate modules etc.
>
> Only after this did I start using the wlan and 3com pcmcia cards and
> ran into the glitch I mailed to the list about.
>
> I hope this helps, and thanks again, I've got my setup working
> smthly now.

It looks like this could be a non-issue, and the installation scripts
are fine.  What do you think?

- Brian



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

debootstrap error installing woody on Powerbook G3

[Ian Collier]

I am doing (or attempting to do) a net install 
of woody using the latest boot new-powermac floppies (files dated April 2nd) on 
my Powerbook G3 (Pismo). (500Mhz, 640MB ram, 10gig free for linux)
 
All seems to go fine until it configuring device 
drivers. When I select 'Next' it pauses a moment and skips straight to 
installing the base system and then while installing base system I get 
"debootstrap exited with an error (return value 139)".
 
Looking in /var/log/messages there is one user.err 
massage about "del_loop ioctl got negative result doing LOOP_CLR_FD on device 
/dev/loop0; this is probably not a big deal"
 
Anyone have any suggestions what might be going 
wrong, or how I can debug further?
 
I did a week or two back manage to install using 
the powermac floppies, but the resulting installation was too unstable to use 
for much, hence the attempt to start over using new-powermac.
 
Cheers,
 
--Ian

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

[Anthony Towns]

On Fri, Apr 05, 2002 at 07:00:08PM +1000, Anthony Towns wrote:
> 2.4 is not the default kernel for woody installs, 2.2 is. 

Oh, and is already clear to everyone involved, this is for i386. Other
ports obviously have 2.4 kernels as default.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

 ``BAM! Science triumphs again!'' 
-- http://www.angryflower.com/vegeta.gif


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

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

[Anthony Towns]

On Fri, Apr 05, 2002 at 10:07:38AM +0200, Eduard Bloch wrote:
> #include 
> Jim Westveer wrote on Thu Apr 04, 2002 um 05:24:24PM:
> > > And last, woody ought to be 2.2 based and not 2.4 based ... but since I
> > > also find it lame to use 2.2.x by default nowadays ...
> > I disagree,  2.4.x kernels have been out for over 2 years.we should
> > not release a "new" version of Debian with such an outdated kernel !
> > [appologies in advance to the boot-floppy group for all their hard work]
> Agreed. The decission, which flavor has to be on the first CD, is done
> by debian-cd's scripts, see
> /usr/share/debian-cd/tools/boot/woody/boot-i386. CD distributors can
> change it if they like.

GUYS, _STOP IT_.

NOW IS _NOT_ THE TIME TO MAKE CHANGES TO THE WAY THE INSTALL WORKS.

2.4 is not the default kernel for woody installs, 2.2 is. Yes, it sucks,
and I don't care. If anyone asks why, blame me. DO NOT MAKE FURTHER
CHANGES TO THE WAY DEFAULT INSTALLS WORK. Not if it makes a billion more
people able to use Debian. Not if it's so fundamentally offensive that
it makes you want to disembowel yourself with a screwdriver.

The default kernel for woody is 2.2. The way languages work is the way
it's worked for the past twelve months. If you want to change stuff,
the time was over six months ago, and it'll be that time again in a
month or two. IT IS _NOT_ NOW.

boot-floppies has exactly two goals right now: make sparc and alpha
boot-floppies work, and make sure that all the successful installs we've
seen so far weren't a collective fantasy.

debian-cd has exactly one goal right now: make sure we're ready to produce
official CDs that include the entire archive and let you get started on
an install.

Cheers,
aj (woody release manager)

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

 ``BAM! Science triumphs again!'' 
-- http://www.angryflower.com/vegeta.gif



msg18274/pgp0.pgp
Description: PGP signature

*****SPAM***** ÀÚ·áÀÔ´Ï´Ù

[ÇÑ°­¼®]

ÀÌ°÷Àº Á¦¸ñÀÔ´Ï´Ù


ÄÄÇ»Å͸¦ ÀÌ¿ëÇϽôµ¥ ²À ÇÊ¿äÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
¾öû Àú·ÅÇÑ °¡°Ý¿¡ ÆË´Ï´Ù

ÃÖ½ÅÇ®¹öÀü°ÔÀÓ. ÄÄÇ»ÅÍ°ü·ÃÇÁ·Î±×·¥.  ¼ºÀνõð µîµî
ÄÄÇ»ÅÍ¿¡ °ü·ÃµÈ ¸ðµç½Ãµð°¡ ÀÖ½À´Ï´Ù

ÃֽŸñ·ÏÀÔ´Ï´Ù
¹°·Ð ½Å¿ëÀº ±âº»ÀÔ´Ï´Ù
¾ÐÃàÈ­ÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ ÀüÈ­³ª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ» º¸³½ ¾ÆÀ̵ð·Î´Â ¿¬¶ôÀÌ µÇÁö ¾Ê½À´Ï´Ù.
¾ÐÃàÈ­Àϼӿ¡ ¿¬¶ôó°¡ ÀÖ½À´Ï´Ù(ÀüÈ­¹øÈ£) 

ÈÞ´ëÆùÀ¸·Î ¿¬¶ôÁֽʽÿä
°¨»çÇÕ´Ï´Ù

³¡À¸·Î Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå¸°°ÍÀ» »ç°úµå¸³´Ï´Ù.±×¸®°í ¿©·¯ºÐÀÇ ¸ÞÀÏÁÖ¼Ò´Â
¹«ÀÛÀ§·Î ¸ð¾ÆÁø°ÍÀÌ´Ï ´Ù¸¥ °ÆÁ¤Àº ÇÏÁö ¾ÊÀ¸¼Åµµ µË´Ï´Ù.  

¸ñ·ÏÀ» ´Ù¿î¹ÞÀ¸½Ã·Á¸é http://homewiz.tripod.lycos.co.kr/board/download.php3?p_id=fkfk997";>ÀÌ°÷À» Ŭ¸¯ÇϽÅÈÄ
cd.zip ¸¦ ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù

¸¸ÀÏ Outlook Express ³ª ´Ù¸¥ ¸ÞÀÏÇÁ·Î±×·¥À»»ç¿ëÇϽô ºÐÁß¿¡ 
¸®½ºÆ®°¡ Á¦´ë·Î ´Ù¿îÀÌ µÇÁö ¾Ê´Â´Ù¸é
÷ºÎµÈ È­ÀÏ ÃÖ½Å.htm À» ¿­°í ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù

½Åû·®¿¡ µû¶ó Ãß°¡½Ãµð¸¦ ¹«·á·Î µå¸®°í ÀÖ½À´Ï´Ù




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

*****SPAM***** ÀÚ·áÀÔ´Ï´Ù

[ÇÑ°­¼®]

ÀÌ°÷Àº Á¦¸ñÀÔ´Ï´Ù


ÄÄÇ»Å͸¦ ÀÌ¿ëÇϽôµ¥ ²À ÇÊ¿äÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
¾öû Àú·ÅÇÑ °¡°Ý¿¡ ÆË´Ï´Ù

ÃÖ½ÅÇ®¹öÀü°ÔÀÓ. ÄÄÇ»ÅÍ°ü·ÃÇÁ·Î±×·¥.  ¼ºÀνõð µîµî
ÄÄÇ»ÅÍ¿¡ °ü·ÃµÈ ¸ðµç½Ãµð°¡ ÀÖ½À´Ï´Ù

ÃֽŸñ·ÏÀÔ´Ï´Ù
¹°·Ð ½Å¿ëÀº ±âº»ÀÔ´Ï´Ù
¾ÐÃàÈ­ÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ ÀüÈ­³ª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ» º¸³½ ¾ÆÀ̵ð·Î´Â ¿¬¶ôÀÌ µÇÁö ¾Ê½À´Ï´Ù.
¾ÐÃàÈ­Àϼӿ¡ ¿¬¶ôó°¡ ÀÖ½À´Ï´Ù(ÀüÈ­¹øÈ£) 

ÈÞ´ëÆùÀ¸·Î ¿¬¶ôÁֽʽÿä
°¨»çÇÕ´Ï´Ù

³¡À¸·Î Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå¸°°ÍÀ» »ç°úµå¸³´Ï´Ù.±×¸®°í ¿©·¯ºÐÀÇ ¸ÞÀÏÁÖ¼Ò´Â
¹«ÀÛÀ§·Î ¸ð¾ÆÁø°ÍÀÌ´Ï ´Ù¸¥ °ÆÁ¤Àº ÇÏÁö ¾ÊÀ¸¼Åµµ µË´Ï´Ù.  

¸ñ·ÏÀ» ´Ù¿î¹ÞÀ¸½Ã·Á¸é http://homewiz.tripod.lycos.co.kr/board/download.php3?p_id=fkfk997";>ÀÌ°÷À» Ŭ¸¯ÇϽÅÈÄ
cd.zip ¸¦ ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù

¸¸ÀÏ Outlook Express ³ª ´Ù¸¥ ¸ÞÀÏÇÁ·Î±×·¥À»»ç¿ëÇϽô ºÐÁß¿¡ 
¸®½ºÆ®°¡ Á¦´ë·Î ´Ù¿îÀÌ µÇÁö ¾Ê´Â´Ù¸é
÷ºÎµÈ È­ÀÏ ÃÖ½Å.htm À» ¿­°í ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù

½Åû·®¿¡ µû¶ó Ãß°¡½Ãµð¸¦ ¹«·á·Î µå¸®°í ÀÖ½À´Ï´Ù




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

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

[Ben Collins]

On Fri, Apr 05, 2002 at 10:07:38AM +0200, Eduard Bloch wrote:
> #include 
> Jim Westveer wrote on Thu Apr 04, 2002 um 05:24:24PM:
> > > And last, woody ought to be 2.2 based and not 2.4 based ... but since I
> > > also find it lame to use 2.2.x by default nowadays ...
> > >
> > 
> > I disagree,  2.4.x kernels have been out for over 2 years.we should
> > not release a "new" version of Debian with such an outdated kernel !
> > [appologies in advance to the boot-floppy group for all their hard work]
> 
> Agreed. The decission, which flavor has to be on the first CD, is done
> by debian-cd's scripts, see
> /usr/share/debian-cd/tools/boot/woody/boot-i386. CD distributors can
> change it if they like.
> IMHO bf2.4 is stable enough to be used as installation
> kernel and is used by most people (Impression, looking at submitter's
> data of recent bug/success reports).
> 
> But who makes this decission for the CD Nr.1? DPL?
> 
> BTW: I personaly think that "compact" on the second CD does not make
> sence, its primarily goal is smart floppy-based installation. 

The DPL makes no such decisions. If anything, the technical committee
would. But I think the port maintainers obviously have the most say in
this.


Ben

-- 
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/


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

cvs commit to boot-floppies/debian by blade

[Debian Boot CVS Master]

Repository: boot-floppies/debian
who:blade
time:   Fri Apr  5 00:12:08 PST 2002
Log Message:
  SUITE -> Woody

Files:
changed:changelog


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

cvs commit to boot-floppies/utilities/dbootstrap by blade

[Debian Boot CVS Master]

Repository: boot-floppies/utilities/dbootstrap
who:blade
time:   Fri Apr  5 00:12:08 PST 2002
Log Message:
  SUITE -> Woody

Files:
changed:extract_base.c


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

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

[Eduard Bloch]

#include 
Jim Westveer wrote on Thu Apr 04, 2002 um 05:24:24PM:
> > And last, woody ought to be 2.2 based and not 2.4 based ... but since I
> > also find it lame to use 2.2.x by default nowadays ...
> >
> 
> I disagree,  2.4.x kernels have been out for over 2 years.we should
> not release a "new" version of Debian with such an outdated kernel !
> [appologies in advance to the boot-floppy group for all their hard work]

Agreed. The decission, which flavor has to be on the first CD, is done
by debian-cd's scripts, see
/usr/share/debian-cd/tools/boot/woody/boot-i386. CD distributors can
change it if they like.
IMHO bf2.4 is stable enough to be used as installation
kernel and is used by most people (Impression, looking at submitter's
data of recent bug/success reports).

But who makes this decission for the CD Nr.1? DPL?

BTW: I personaly think that "compact" on the second CD does not make
sence, its primarily goal is smart floppy-based installation. 

Gruss/Regards,
Eduard.
-- 
Beim Reparieren von Elektrogeräten kann einem schlagartig
   klar werden, wo der Fehler liegt.


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