Re: netinst asks for basedebs.tar ?

[Junichi Uekawa]

Manuel Clos <[EMAIL PROTECTED]> cum veritate scripsit:

> Hi all,
> 
> where should I get the basedebs.tar that the netinst CD ask for when I 
> select "Install Base System" ?

The current situation is that you are supposed to roll your own
using debootstrap.


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]

[광고]설날최고의 효도선물~일본열도강타~!!한국북상륙!!

[삼일사]

³×¶¼·ç¸¶´Ï °í°´°¨»ç À̺¥Æ®!!~~.

 2002³â1¿ù10ÀϺÎÅÍ~
ÀúÈñ ³×¶¼·ç¸¶´Ï ½ÅûÀÚ ¸ðµÎ¿¡°Ô ¶Ç´Ù¸¥ À̺¥Æ® Çà»ç¸¦ ¸¶·Ã ÇÏ¿´½À´Ï´Ù.
A¼¼Æ®+2Æ÷+ÄíÆù1Àå, B¼¼Æ®+4Æ÷+ÄíÆù2Àå, C¼¼Æ®+10Æ÷+ÄíÆù6Àå
ÄíÆùÀ»10Àå ¸ð¾Æ¼­ ÀúÈñ¿¡°Ô º¸³» Áֽøé A¼¼Æ® 1¹Ú½º¸¦ ¹«·á·Î º¸³» µå¸®°í ÀÖÀ¸´Ï ¸¹ÀÌ Âü¿© ÇϽñ⠹ٶø´Ï´Ù



³×¶¼·ç¸¶´Ï
¼³³¯ÃÖ°íÀÇ È¿µµ»óÇ°..³×¶¼·ç¸¶´ÏÀÔ´Ï´Ù. 
ÃÖ°íÀÇ È¿µµ»óÇ°..³×¶¼·ç¸¶´ÏÀÔ´Ï´Ù. 
¿¬¸»¿¬ÃÊ Çà»çÀǼ±¹°ÀÇ ÀÏÀÎÀÚ.. ³×¶¼·ç¸¶´ÏÀÔ´Ï´Ù 


  Àáµç µ¿¾ÈÀ̶ó´Â ÀϺ» ¸»À̸ç ÀϺ» (À¯ÇÑȸ»ç) 
¶óÀÌÇÁ21»çÀÇ ³ª°¡´Ù »çÀåÀÌ ³²ÆíÀÇ ¾ÏÀ» Ä¡·áÂ÷ 
ºê¶óÁú¿¡ °¡¼­ ¾Æ°¡¸®Äí½º ¹ö¼¸À» ÀÌ¿ëÇÏ¿© 
Ä¡·áÇÑ °ÍÀ» °è±â·Î ÀϺ»ÀÇ ¹Î°£¿ä¹ýÀÎ ¸ñÃÊ¾× 
»ç¿ë¹ý°ú Á¢¸ñ, ¹ßÀü½ÃÄÑ ¾²±â °£ÆíÇÏ°Ô ¾Æ°¡¸®Äí½º 
¹ö¼¸, À¯Ä«¸® ¼ö¾×, ÀüºÐÀ» Ưº°ÇÑ Á¦Á¶¹ýÀ¸·Î 
ºÐ¸»È­ÇÏ¿© ÇÑÁö·Î °¡°øÇÑ È­Á¦ÀÇ ¼ö¾×½ÃÆ®·Î 
½ÀÆ÷Á¦Ã³·³ ¹ß¹Ù´ÚÀ̳ª ¾ÆÇ °÷¿¡ ºÙÀÌ¸é ³ª¹«»Ñ¸®°¡ 
¼öºÐÀ» »¡¾Æ¿Ã¸®´Â °Íó·³ ¹ß¹Ù´ÚÀ¸·ÎºÎÅÍ 
¸ö ¼ÓÀÇ ³ëÆó¹°À» »Ì¾Æ³»¾î ½Å±âÇÏ°Ô ¸öÀÌ 
°¡»ÓÇÏ°í »óÄèÇØÁý´Ï´Ù.Áï, ÆĽºÀÇ ÇüÅ·Π
ºÎȲ°ú °í¾àÀÇ ¿ªÇÒÀ» ÇÏ´Â °ÍÀÔ´Ï´Ù.Á»´õ 
°£´ÜÈ÷ ¸»ÇÏ¸é ¸ð¾çÀº ÆĽºÀÇ ÇüÅÂÁö¸¸ ±â´ÉÀº 
¸ö¼ÓÀÇ ³ëÆó¹°À» °­·ÂÇÏ°Ô »¡¾Æ³»´Â ºÎȲ°ú 
°í¾àÀ» ÇÕÄ£ °Í°ú °°´Ù°í ÇÒ ¼ö ÀÖ½À´Ï´Ù.Áï, 
ÆĽºÃ³·³ °£ÆíÈ÷ ºÎÂøÇÏ°í ¹ß¹Ù´Ú¿¡ ºÙ¿© ¸ö 
¼ÓÀÇ ³ëÆó¹°À» »¡¾Æ³»´Â °ÍÀÔ´Ï´Ù. 


ºÎ¸ð´Ôµé¿¡°Ô´Â ´õ´õ¿í À̺¸´Ù ÁÁÀº ¼±¹°Àº ¾øÀ»°ÍÀÔ´Ï´Ù. 
www.si.co.kr·Î 
Áö±Ý ¹Ù·Î µé¾î¿À¼¼¿ä.


	
	
		
		
  
		- "Á¤º¸Åë½Å¸ÁÀÌ¿ëÃËÁøµî¿¡°üÇѹý·ü½ÃÇà±ÔÄ¢°³Á¤·É"¿¡ ÀÇ°Å Á¦¸ñ¿¡ [±¤°í]¶ó Ç¥½ÃµÈ ±¤°í ¸ÞÀÏÀÔ´Ï´Ù.
		- ¸ÞÀϼö½Å°ÅºÎ¸¦ ÇÏ½Ç °æ¿ì ´õ ÀÌ»ó ¸ÞÀÏÀÌ °¡Áö ¾Ê½À´Ï´Ù.
		- ±ÍÇÏÀÇ email ID´Â °Ô½ÃÆÇ µî ±âŸ °ø°³µÈ ÀÚ·á¿¡¼­ ¼öÁýµÈ °ÍÀ¸·Î ÀÌ»óÀÇ ´Ù¸¥ °³ÀÎÁ¤º¸´Â ¾ø½À´Ï´Ù.
		- email ¼­ºñ½º¸¦ ¿øÇÏÁö ¾ÊÀ¸½Ã¸é 
 
 ¸¦ Ŭ¸¯Çϼ¼¿ä. 
  
		
	
		

netinst asks for basedebs.tar ?

[Manuel Clos]

Hi all,

where should I get the basedebs.tar that the netinst CD ask for when I 
select "Install Base System" ?

Thanks.

-- 
Manuel Clos
[EMAIL PROTECTED]

* Si no puedes hacerlo bien, hazlo bonito (Bill Gates)
* If you can't do it well, do it nice (Bill Gates)


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

Re: Adaptec ATA Raid 2400A and Woody

[Chris Tillman]

On Thu, Jan 24, 2002 at 11:48:15AM +0200, George Papamichelakis wrote:
> Hello,
> 
> I have managed to install woody on a system that uses
> the above adaptec card. I had at first to use a minimum
> potato installation on a separate disk and then upgrade
> to woody, install a 2.4 kernel and then use the dpt_i2o
> module to see the raid disk. A friend of mine wishes
> to use the same card on a system but he wants to make 
> a fresh install directly on the raid device. There aren't
> any woody disks with kernel 2.4 as far as I can tell.
> Does anybody have a workaround for this ?
> 
> George Papamichelakis

lists.debian.org/debian-boot/2002/debian-boot-200201/msg00437.html

Always good to search the archives before posting.

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

Re: WTF is with dhcp?

[Glenn McGrath]

On Thu, 24 Jan 2002 18:57:18 +0100 (CET)
"Jerome Petazzoni" <[EMAIL PROTECTED]> wrote:

> 
> [talking about dhcp server packages...]
> > Now, I would have liked to upload my experimental packages for the
3.x> > series a long time ago (October 5, 2001 that was when DHCP ISC
3.0 was> > released.) The problem is that the boot floppies are using
the DHCP> > client from the 2.x series. The client in the 3.x series is
too big> > to be handled now by the boot floppies so when I mentioned
that I was> > ready to upload to unstable my 3.x packages I was told to
wait: > 
> why not use udhcpc in the boot floppies ? it's really small.
> there was a few mails about that in september, 2001 ; and I
> can't remember major objections, except lack of testing for
> compatibility with misc. dhcp servers. if nobody wants/has
> the time to integrate udhcpc in boot floppies, well, I might
> just as well volunteer (but I am currently totally ignorant
> of the internal of boot floppies).

Ive been using udhcpc for a few months and havent had any problems, it
is getting late to be changeing things around though.


Glenn


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

Re: Bug#130482: 3.0.19 show-stoppers

[Anthony Towns]

On Thu, Jan 24, 2002 at 06:38:40PM +0100, Stefan Gybas wrote:
> On Thu, Jan 24, 2002 at 09:06:17AM -0800, Matt Kraai wrote:
> > I object.  We should fix, rather than disable, it.  Could you
> > please try the following code instead?
> Sorry, I won't have access to the s390 systems until Monday so I
> can't do this now. I have uploaded the NMU for i386 and s390 to
> incoming - if you or anybody else objects, just remove the files
> there.

Uh. You didn't file bugs for the things you fixed, nor did you send a
patch to the BTS. That is incredibly poor form.

> debootstrap 0.1.15.x did not contain the initctl patch and worked
> fine 

It worked fine on some architectures, and not others.

> It already took me several hours to find the problem so I'm not very
> interested in spending even more time trying different variants of
> this hack.

If this is your attitude to the package, then you shouldn't be NMUing
the package. Either get it right, or don't do it at all.

Cheers,
aj

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

The daffodils are coming. Are you?
  linux.conf.au, February 2002, Brisbane, Australia
--- http://linux.conf.au/



msg15100/pgp0.pgp
Description: PGP signature

Bug#129479: scsi disk not detected

[Chris Tillman]

On Thu, Jan 24, 2002 at 08:56:00AM +0100, Manuel Quesada wrote:
> > Maybe the installer is trying to mount /dev/hda, which would be a
> > standard type disk on a newWorld. Try switching to virtual console 2,
> > or use the Execute a Shell menu command, to enter
> >
> > mac-fdisk /dev/sda
> >
> > After partitioning it the linux partitions will definitely be visible
> > to the installer.
> >
> > --
> > *--v- Installing Debian GNU/Linux 3.0 v--*
> > |    |
> > |   debian-imac (potato):    |
> > |Chris Tillman[EMAIL PROTECTED]  |
> > |   May the Source be with you   |
> > **
> 
> I did it, but didn' work. It can'f find the device.

Well, certainly, you do not have a scsi disk that mac-fdisk can
find. Is it by chance a pc-formatted scsi? mac-fdisk would try to read
the partition table at the beginning of the disk, which is an Apple
format. 

Possibly you could use Drive Setup to initialize the disk (if you have
MacOS available). If you don't have MacOS, and you have a floppy (but
this was an iMac, wasn't it?) you could use the downloadable MacOS
Disk Tools floppy to do that.

If you have another Linux system, you could always connect the drive
in to that system to get it initialized or even to install on it, and
then move it back.

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

Re: Things we need from sid

[Eduard Bloch]

#include 
Herbert Xu wrote on Fri Jan 25, 2002 um 08:42:47AM:

> > kernel-image-2.4.x series for unuseable for most people. YOU KNOW THIS.
> > Manoj tries to do the best job - he often fixed the bugs quickly when I
> > reported something (and you often ignored this fixes). 
> 
> More FUD.

I know, all arguments not agreed by you count as FUD.

> b) is absolutely unnecessary unless you've been listening to
> Eduard Bloch and have put crap into it.

I forgot to delete this - in the moment, I just remembered that the user
will still fail to change to ext3 (putting "auto" in fstab as described
in howtos), since you refused to apply my patch from #126889 and closed
the report instead. Good work.

> c) is something that has to be done anyway.

Sooner or later. Definitely later when installing Debian with a working 2.4 kernel.

> IMHO the current preinst/postinst scripts already handle it
> satisfactorily.

You know that this is a critical point and can cause
much frustration if something goes wrong. And it can go wrong.

> And the current release of 2.4.17 has no known initrd bugs.

I hope so.

> > Go and install with floppy disks, or fetch the packages with an
> > osziloscope and a hex editor. Have fun.
> I'd like to see you put the base system on floppies...

Yeah, remove your previous statement and make this sentence appear in
the wrong light...

> > > As long as the one in 2.2 works to the extent that an installation can
> > > be done, this is irrelevant.
> > 
> > How many people do replace the kernel just after the base install?
> 
> Probably quite a few.  Anyway, this is a documentation issue.

So? Then I will tell my impression so far:

I try to:

 - limit number of flavors (getting more space for usefull programs on
   the CDs)
 - replace the patched flavors with a better solution
 - give users more freedom to choose the installation source
 - provide a smooth way for configuring the hardware (see previous mails)

You try to:

 - tell everyone that the new drivers are not needed
 - say that the current solution will be good for everyone, and for the
   next 1-2 years (release cycle), using a kernel which stopped beeing
   developed almost a year ago
 - say that everything is a documentation issue. People should better
   read docs and curse about complicated configuration with Debian
 - force everyone who wants 2.4 to use your, and only your packages

Finally, the new flavor does not cost YOU much. The vanilla installation
disk will still use 2.2.20. bf2.4 kernel package does not require your
to do anything but keeping the kernel-source as bug-free as possible. So
what are we talking about?

> > Count the drivers in 2.4.
> 
> All the important USB network drivers are already in 2.2.20.

Importance changes with the number of sold devices. Having an
installation option with kernel 2.4 is like an investment into the
future compatibility.

Gruss/Regards,
Eduard.
-- 
 hmhm... hier ist bestimmt niemand, dem die begriffe RED und ns im
kontext netzwerke was sagen, oder?
 Y_Plentyn: rot kennt jeder, und ueber NS redet man nicht mehr...
-- #debian.de


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

Re: Things we need from sid

[Herbert Xu]

On Thu, Jan 24, 2002 at 09:55:50PM +0100, Eduard Bloch wrote:
>
> > > > A 2.4 kernel is only an apt-get install away so this has no place when
> > > 
> > > Blah. You should know better than me that this is not true.
> > 
> > Please give details.
> 
> Please? You have to a) install, b) change fstab, c) change boot loader's
> configuration. Handling with initrd is more dangerous than a kernel with
> statical configuration. There were bugs in make-kpkg which made
> kernel-image-2.4.x series for unuseable for most people. YOU KNOW THIS.
> Manoj tries to do the best job - he often fixed the bugs quickly when I
> reported something (and you often ignored this fixes). 

More FUD.  b) is absolutely unnecessary unless you've been listening to
Eduard Bloch and have put crap into it.  c) is something that has to be
done anyway.  IMHO the current preinst/postinst scripts already handle it
satisfactorily.

And the current release of 2.4.17 has no known initrd bugs.

> Go and install with floppy disks, or fetch the packages with an
> osziloscope and a hex editor. Have fun.

I'd like to see you put the base system on floppies...

> > It's funny that you raise tulip, because the tulip driver in 2.2 in fact
> > works much better than the one in 2.4.
> 
> Really funny. Once I removed the tulip patch from the
> kernel-patch-ethernet-drivers package, I got a request to readd it.

That's Donald Becker's driver, something completely different and it
doesn't work in 2.4 anyway.

> > As long as the one in 2.2 works to the extent that an installation can
> > be done, this is irrelevant.
> 
> How many people do replace the kernel just after the base install?

Probably quite a few.  Anyway, this is a documentation issue.
 
> > >  - newer USB network hardware is not supported by 2.2.20. Same for other
> > >possible installation media.
> > 
> > Like what?
> 
> Count the drivers in 2.4.

All the important USB network drivers are already in 2.2.20.
-- 
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]

Re: Things we need from sid

[Matt Zimmerman]

On Thu, Jan 24, 2002 at 08:42:29PM +0100, Eduard Bloch wrote:

> Not providing an Ext3 option as-default would damage Debian's reputation.

If we are worried about reputations, the best thing to do is to get a
release out the door with updated versions of common user packages.  Users
who want a release that they can install and use are much more numerous than
users who cannot convert to ext3 post-install.

-- 
 - mdz


-- 
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:   tor jan 24 22:15:33 CET 2002
Log Message:
  Translation updates.

Files:
changed:sv.po


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

Re: Things we need from sid

[Eduard Bloch]

#include 
Herbert Xu wrote on Fri Jan 25, 2002 um 07:25:13AM:

> >  - This are patches
> >  - ide patched kernel is reported to hang on some new chipsets while IDE
> >detection
> 
> Please give specific details rather than vague recollections.

Both people were newbies - and how should a newbie report something if
he cannot install Debian?

> > 2.4 uses reiserfs-3.6 as default, 2.2.20 does not (and apparently will
> > never) support it. Imagine someone downloads the Debian stuff to a
> > ReiserFS partition under SuSE/RedHat (where reiserfs-3.6 has been used
> > for epochs) and tries to mount it.
> 
> Please recall that we're discussing boot floppies here so existing file
> systems do not matter.

If you cannot access the installation source, it does matter.

> > > Ext3 does not need boot floppies support.  Conversion after installation
> > > of a 2.4 kernel is trivial.
> > 
> > Not providing an Ext3 option as-default would damage Debian's reputation.
> 
> FUD.

Your opinion. Many people have another one.

> > > A 2.4 kernel is only an apt-get install away so this has no place when
> > 
> > Blah. You should know better than me that this is not true.
> 
> Please give details.

Please? You have to a) install, b) change fstab, c) change boot loader's
configuration. Handling with initrd is more dangerous than a kernel with
statical configuration. There were bugs in make-kpkg which made
kernel-image-2.4.x series for unuseable for most people. YOU KNOW THIS.
Manoj tries to do the best job - he often fixed the bugs quickly when I
reported something (and you often ignored this fixes). 

> >  - working Plug-and-Play. As someone in the list allready reported, we
> >allways have a problem with isapnp cards. Do you want a clueless
> >user to change to a second console and work with pnpdump and isapnp
> >just to make the damn thing work?
> 
> Not required for installation.

Go and install with floppy disks, or fetch the packages with an
osziloscope and a hex editor. Have fun.

> >  - network cards. You did include the natsemi driver - wow. But what
> >about many other cards and new releases (such as for Tulip cards),
> >which are not supported by 2.2.x?
> 
> It's funny that you raise tulip, because the tulip driver in 2.2 in fact
> works much better than the one in 2.4.

Really funny. Once I removed the tulip patch from the
kernel-patch-ethernet-drivers package, I got a request to readd it.

> >  - new ide chipsets. 2.4 has more and and much stable drivers.
> 
> As long as the one in 2.2 works to the extent that an installation can
> be done, this is irrelevant.

How many people do replace the kernel just after the base install?

> >  - newer ISDN drivers. People installing with a (often sold) Fritc-PCIv2
> >card would "thank" us for using kernel-2.2.x.
> 
> Irrelevant for an installation.

Everything that can fetch data from a public source is relevant for the
installation.

> >  - newer USB network hardware is not supported by 2.2.20. Same for other
> >possible installation media.
> 
> Like what?

Count the drivers in 2.4.

Gruss/Regards,
Eduard.
-- 
Die 3 goldenen R's bei Microsoft Systemen:
Retry, Reboot, Reinstall .
 (Joerg Schilling)


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

Re: Things we need from sid

[John H. Robinson, IV]

On Fri, Jan 25, 2002 at 07:25:13AM +1100, Herbert Xu wrote:
> > > 
> > > IMHO reiserfs simply isn't viable anymore.  So I don't really care

please explain - how is it ``not viable anymore''? replaced by ext3? the
only thing ext3 has is journalling. reiserfs brings a lot more to the
table than simply journalling.

> > 2.4 uses reiserfs-3.6 as default, 2.2.20 does not (and apparently will
> > never) support it. Imagine someone downloads the Debian stuff to a
> > ReiserFS partition under SuSE/RedHat (where reiserfs-3.6 has been used
> > for epochs) and tries to mount it.
> 
> Please recall that we're discussing boot floppies here so existing file
> systems do not matter.

not true. the basedebs.tgz could have been downloaded by the SuSE
alt-boot reiserfs partition. /usr/local could be shared between the
Debian and Red Hat boots, which could easily be reiserfs.

this is not a non-issue, but a real and valid one.

the latter can be worked around by upgrading the kernel to 2.4.x
after the install, then adding the /usr/local to fstab. the
former cold only be worked around by putting the basedebs.tgz on
a non-reiser partition. the same issue faced by those using xfs.

-john

disclaimer: i happily run 2.2.20.


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

Debian 22r4 on Asus A7V 133 (U-ATA 100)

[K. Werner]

Hi there, 
 
I do have a problem installing Debian 2.2r4 on my Asus A7V 133 - U-ATA 100 
by Promise onboard Chip (my guess is that the problem is caused by this fellow). 
I downloaded the installation/rescue discs from Debian, they are booting but the 
installation routine cannot find my harddisk (IBM DTLA-307030), later on it is 
also unable to find my Ethernet card (noname with realtek chip rtl8139).
Installing SUSE with Kernel 2.4.4 is no problem, so the hardware is 
o.k.
 
Has anyone heard of a workaround for this problem?
 
Thanks in advance
 
K. Werner

Re: Things we need from sid

[Herbert Xu]

On Thu, Jan 24, 2002 at 08:42:29PM +0100, Eduard Bloch wrote:
>
> > Without initrd, you can include only so many hardware drivers.  And for all
> > of the important drivers that I can think of (such as NetGear FA311TX,
> > AICRAID, Promise Ultra IDE etc.), the support is already in at least one of
> > the latest 2.2 images anyway.
> 
>  - This are patches
>  - ide patched kernel is reported to hang on some new chipsets while IDE
>detection

Please give specific details rather than vague recollections.

> > 2. Support for ext3/reiserfs.
> > 
> > IMHO reiserfs simply isn't viable anymore.  So I don't really care
> 
> 2.4 uses reiserfs-3.6 as default, 2.2.20 does not (and apparently will
> never) support it. Imagine someone downloads the Debian stuff to a
> ReiserFS partition under SuSE/RedHat (where reiserfs-3.6 has been used
> for epochs) and tries to mount it.

Please recall that we're discussing boot floppies here so existing file
systems do not matter.

> > Ext3 does not need boot floppies support.  Conversion after installation
> > of a 2.4 kernel is trivial.
> 
> Not providing an Ext3 option as-default would damage Debian's reputation.

FUD.

> > 3. Better support for auxiliary hardware such as sound cards.
> > 
> > A 2.4 kernel is only an apt-get install away so this has no place when
> 
> Blah. You should know better than me that this is not true.

Please give details.


> > If there is another important reason for a 2.4 kernel, please let me know.
> 
> As you wish:
> 
>  - the 64MB detection limit, AFAIK this has been fixed in 2.4

No this was first fixed in 2.2.

>  - working Plug-and-Play. As someone in the list allready reported, we
>allways have a problem with isapnp cards. Do you want a clueless
>user to change to a second console and work with pnpdump and isapnp
>just to make the damn thing work?

Not required for installation.

>  - network cards. You did include the natsemi driver - wow. But what
>about many other cards and new releases (such as for Tulip cards),
>which are not supported by 2.2.x?

It's funny that you raise tulip, because the tulip driver in 2.2 in fact
works much better than the one in 2.4.

>  - new ide chipsets. 2.4 has more and and much stable drivers.

As long as the one in 2.2 works to the extent that an installation can
be done, this is irrelevant.

>  - newer ISDN drivers. People installing with a (often sold) Fritc-PCIv2
>card would "thank" us for using kernel-2.2.x.

Irrelevant for an installation.

>  - newer USB network hardware is not supported by 2.2.20. Same for other
>possible installation media.

Like what?
-- 
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]

Re: Things we need from sid

[Eduard Bloch]

#include 
Herbert Xu wrote on Thu Jan 24, 2002 um 07:59:52PM:

> > So are these an official part of boot-floppies? Should they be being
> > (co?)maintained by Herbert to keep them in sync with the other kernels?

No. I allow to update the package and NMU if I do not respond for >=2
days, but Herbert should keep his hands of it.

> I would be happy to do so if someone can show me why we really need 2.4

I can imagine that you will do, but then I worry about the future
of the package.

> Without initrd, you can include only so many hardware drivers.  And for all
> of the important drivers that I can think of (such as NetGear FA311TX,
> AICRAID, Promise Ultra IDE etc.), the support is already in at least one of
> the latest 2.2 images anyway.

 - This are patches
 - ide patched kernel is reported to hang on some new chipsets while IDE
   detection

> 2. Support for ext3/reiserfs.
> 
> IMHO reiserfs simply isn't viable anymore.  So I don't really care

2.4 uses reiserfs-3.6 as default, 2.2.20 does not (and apparently will
never) support it. Imagine someone downloads the Debian stuff to a
ReiserFS partition under SuSE/RedHat (where reiserfs-3.6 has been used
for epochs) and tries to mount it.

> Ext3 does not need boot floppies support.  Conversion after installation
> of a 2.4 kernel is trivial.

Not providing an Ext3 option as-default would damage Debian's reputation.

> 3. Better support for auxiliary hardware such as sound cards.
> 
> A 2.4 kernel is only an apt-get install away so this has no place when

Blah. You should know better than me that this is not true.

> If there is another important reason for a 2.4 kernel, please let me know.

As you wish:

 - the 64MB detection limit, AFAIK this has been fixed in 2.4
 - working Plug-and-Play. As someone in the list allready reported, we
   allways have a problem with isapnp cards. Do you want a clueless
   user to change to a second console and work with pnpdump and isapnp
   just to make the damn thing work?
 - network cards. You did include the natsemi driver - wow. But what
   about many other cards and new releases (such as for Tulip cards),
   which are not supported by 2.2.x?
 - new ide chipsets. 2.4 has more and and much stable drivers.
 - newer ISDN drivers. People installing with a (often sold) Fritc-PCIv2
   card would "thank" us for using kernel-2.2.x.
 - newer USB network hardware is not supported by 2.2.20. Same for other
   possible installation media.

Gruss/Regards,
Eduard.
-- 
Letzte Worte des Computers: "Sind Sie sicher? (J/N)"


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

Re: problem with debootstrap and boot-floppies

[Matt Kraai]

On Thu, Jan 24, 2002 at 04:42:31PM -0200, Gustavo Noronha Silva wrote:
> I found out that debootstrap 0.1.16 uses mkfifo on its
> scripts (/usr/lib/debootstrap/scripts/{woody,sid})
> but it is not available on the boof-floppies' system
> 
> I worked it around using mknod $i p, I didn't file
> a bug on it, do what you think that it is needed

Stefan Gybas is preparing a debootstrap NMU which skips the
section of code that calls mkfifo, thus avoiding the problem.

Matt



msg15089/pgp0.pgp
Description: PGP signature

cvs commit to debian-installer/doc by tfheen

[Debian Boot CVS Master]

Repository: debian-installer/doc
who:tfheen
time:   Thu Jan 24 10:51:27 PST 2002
Log Message:
  Update URL to UPX.
  

Files:
changed:README


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

problem with debootstrap and boot-floppies

[Gustavo Noronha Silva]

[cc me on replies]

Hello friends!

I found out that debootstrap 0.1.16 uses mkfifo on its
scripts (/usr/lib/debootstrap/scripts/{woody,sid})
but it is not available on the boof-floppies' system

I worked it around using mknod $i p, I didn't file
a bug on it, do what you think that it is needed

[]s!

-- 
Gustavo Noronha Silva - kov 
*-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+
|  .''`.  | Debian GNU/Linux:  |
| : :'  : + Debian BR...: +
| `. `'`  + Q: "Why did the chicken cross the road?"  +
|   `-| A: "Upstream's decision." -- hmh  |
*-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+


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

Re: WTF is with dhcp?

[Jerome Petazzoni]

[talking about dhcp server packages...]
> Now, I would have liked to upload my experimental packages for the 3.x
> series a long time ago (October 5, 2001 that was when DHCP ISC 3.0 was
> released.) The problem is that the boot floppies are using the DHCP
> client from the 2.x series. The client in the 3.x series is too big
> to be handled now by the boot floppies so when I mentioned that I was
> ready to upload to unstable my 3.x packages I was told to wait: 

why not use udhcpc in the boot floppies ? it's really small.
there was a few mails about that in september, 2001 ; and I
can't remember major objections, except lack of testing for
compatibility with misc. dhcp servers. if nobody wants/has
the time to integrate udhcpc in boot floppies, well, I might
just as well volunteer (but I am currently totally ignorant
of the internal of boot floppies).

sorry if that matter has been discuted again recently, but
a quick google search yielded nothing new about it ...

Jerome Petazzoni 


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

cvs commit to boot-floppies/s390-specials by sgybas

[Debian Boot CVS Master]

Repository: boot-floppies/s390-specials
who:sgybas
time:   Thu Jan 24 09:38:54 PST 2002
Log Message:
  Fixed parsing of dbootstrap return code
  

Files:
changed:root.profile


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

Re: 3.0.19 show-stoppers

[Stefan Gybas]

On Thu, Jan 24, 2002 at 09:06:17AM -0800, Matt Kraai wrote:

> I object.  We should fix, rather than disable, it.  Could you
> please try the following code instead?

Sorry, I won't have access to the s390 systems until Monday so I
can't do this now. I have uploaded the NMU for i386 and s390 to
incoming - if you or anybody else objects, just remove the files
there.

debootstrap 0.1.15.x did not contain the initctl patch and worked
fine so I don't see why this should be enabled for the boot-floppies.
sysvinit in woody was fixed to not signal PID 1 if /dev/initctl does
not exist. debootstrap 0.1.16 definitely does not work on s390, so I
can either build s390 b-fs with my NMU or stay with 0.1.15.9. It
already took me several hours to find the problem so I'm not very
interested in spending even more time trying different variants of
this hack.

-- 
Stefan Gybas


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

Re: 3.0.19 show-stoppers

[Matt Kraai]

On Thu, Jan 24, 2002 at 04:21:28PM +0100, Stefan Gybas wrote:
> On Thu, Jan 24, 2002 at 01:36:37PM +0100, Stefan Gybas wrote:
> 
> > I'll make this change in my NMU which fixes the s390 problems.
> 
> Testing with current CVS boot-floppies on s390 shows that this section
> does not work. It causes dbootstrap to hang after calling debootstrap
> (maybe because the cat process isn't properly killed?) and all packages
> have been set up. The last message is "I: debootstrap: Successfully
> completed" from exec_debootstrap() in extract_base.c - the rest is not
> executed:
> 
> mkfifo $TARGET/dev/initctl
> cat <$TARGET/dev/initctl >/dev/null &
> CAT_PID=$!
> on_exit "kill $CAT_PID >/dev/null 2>&1"
> 
> I'd like to disable this section for the boot-floppies, it's not
> necessary there:
> 
> if [ -n "$USE_BOOTFLOPPIES_INTERACTION" ]; then
> mknod -m 600 $TARGET/dev/initctl p
> cat <$TARGET/dev/initctl >/dev/null &
> CAT_PID=$!
> on_exit "kill $CAT_PID >/dev/null 2>&1"
> fi
> 
> Any objections? Does the old section work on other architectures?

I object.  We should fix, rather than disable, it.  Could you
please try the following code instead?

mknod $TARGET/dev/initctl
tail -f <$TARGET/dev/initctl >/dev/null &
TAIL_PID=$!
on_exit "kill $TAIL_PID"

Matt



msg15083/pgp0.pgp
Description: PGP signature

Re: 3.0.19 show-stoppers

[Stefan Gybas]

On Thu, Jan 24, 2002 at 04:21:28PM +0100, Stefan Gybas wrote:

> if [ -n "$USE_BOOTFLOPPIES_INTERACTION" ]; then
   ^^

Sorry, this must be -z, of course.

-- 
Stefan Gybas


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

Bug#118997: Related issue to 118997

[Matt Kraai]

On Thu, Jan 24, 2002 at 11:56:31AM +1000, Anthony Towns wrote:
> The "auto" line probably shouldn't appear for PCMCIA cards. (auto means
> "configure this interface at bootup", whereas PCMCIA cards are only
> configured when the card's inserted)

Thanks for pointing that out.  Could someone please test the
following patch?

Matt

Index: netconfig.c
===
RCS file: /cvs/debian-boot/boot-floppies/utilities/dbootstrap/netconfig.c,v
retrieving revision 1.80
diff -u -p -r1.80 netconfig.c
--- netconfig.c 2002/01/03 19:19:54 1.80
+++ netconfig.c 2002/01/24 16:04:05
@@ -32,8 +32,6 @@
 #define NC_ETC_NETWORK_DIR "/etc/network"
 #define NC_INTERFACES_FILE "/etc/network/interfaces"
 #define NC_HOSTS_FILE  "/etc/hosts"
-#define NC_PCMCIA_DIR  "/etc/pcmcia"
-#define NC_PCMCIA_FILE "/etc/pcmcia/network.opts"
 /* 
   Use 2.2.x because dhclient forces -q (quiet) and I like logging.
   Using dhclient would make adding 2.0.x support just a matter of 
@@ -634,73 +632,6 @@ int write_common_network() {
 }
 
 
-#ifdef PCMCIA
-/*
- * Write the PCMCIA network configuration (static and DHCP)
- */
-int write_pcmcia_network() {
-  FILE *p_file;
-  char *tmp, *ns, *aux;
-  const char* path;
-  int ix;
-
-  path = target_path(NC_PCMCIA_DIR);
-  if (check_dir(path) == -1) mkdir(path, 0755);
-  
-  if ((p_file = fopen(target_path(NC_PCMCIA_FILE), "w"))) {
-fprintf(p_file, "# Network adapter configuration\n#\n# Automatically generated 
during the Debian installation\n#\n");
-fprintf(p_file, "# The address format is 
\"scheme,socket,instance,hwaddr\".\n#\ncase \"$ADDRESS\" in\n*,*,*,*)\n");
-fprintf(p_file, "\t# Transceiver selection, for some cards -- see 'man 
ifport'\n");
-if (transceiver) {
-  fprintf(p_file, "\tIF_PORT=\"%s\"\n", transceiver);
-} else {
-  fprintf(p_file, "\tIF_PORT=\"\"\n");
-}
-if(use_dhcp) {
-  if( NAME_ISEXE( NC_DHCLIENT_FILE, &nc_statbuf )) 
- fprintf(p_file, "\tDHCLIENT=\"y\"\n");
-  else
-  fprintf(p_file, "\tPUMP=\"y\"\n");
-} else {
-  fprintf(p_file, "\tPUMP=\"n\"\n");
-  fprintf(p_file, "\t# Host's IP address, netmask, network address, broadcast 
address\n");
-  fprintf(p_file, "\tIPADDR=\"%s\"\n", IP4tostr(prtbuf, ipaddr));
-  fprintf(p_file, "\tNETMASK=\"%s\"\n", IP4tostr(prtbuf, netmask));
-  fprintf(p_file, "\tNETWORK=\"%s\"\n", IP4tostr(prtbuf, network));
-  fprintf(p_file, "\tBROADCAST=\"%s\"\n", IP4tostr(prtbuf, broadcast));
-  if (has_gw) {
-fprintf(p_file, "\tGATEWAY=\"%s\"\n", IP4tostr(prtbuf, gateway));
-  } else {
-fprintf(p_file, "\tGATEWAY=\"\"\n");
-  }
-  if (domain) {
-fprintf(p_file, "\tDOMAIN=\"%s\"\n", domain);
-  }
-  if (nameserver) {
-aux = ns = strdup(nameserver);
-ix = 1;
-while ((tmp = strchr(ns, ' ')) != NULL) {
-  *tmp = '\0';
-  tmp++;
-  fprintf(p_file, "\tDNS_%d=\"%s\"\n", ix, ns);
-  ns = tmp;
-  ix++;
-}
-fprintf(p_file, "\tDNS_%d=\"%s\"\n", ix, ns);
-free(aux);
-  } else {
-fprintf(p_file, "\tDNS_1=\"\"\n");
-  }
-}
-fprintf(p_file, "\t;;\nesac\n");
-fclose(p_file);
-return 0;
-  } else {
-return 255;
-  }
-}
-
-#endif /* PCMCIA */
 
 /*
  * Write the static network configuration
@@ -756,36 +687,29 @@ int write_static_network() {
   } else {
 ret = 255;
   }
-#ifdef PCMCIA
-  /*
-   * Only write /etc/network/interfaces if we have a non-PCMCIA interface.
-   */
-  if (has_pcmcia) {
-ret = write_pcmcia_network();
-  } else 
-#endif /* PCMCIA */
-  {
-if ((p_file = fopen(target_path(NC_INTERFACES_FILE), "a"))) {
-  fprintf(p_file, "\n# The first network card - this entry was created during the 
Debian installation\n");
-  fprintf(p_file, "# (network, broadcast and gateway are optional)\n");
+
+  if ((p_file = fopen(target_path(NC_INTERFACES_FILE), "a"))) {
+fprintf(p_file, "\n# The first network card - this entry was created during the 
+Debian installation\n");
+fprintf(p_file, "# (network, broadcast and gateway are optional)\n");
+if (!has_pcmcia)
   fprintf(p_file, "auto %s\n", netinterface);
-  fprintf(p_file, "iface %s inet static\n", netinterface);
-  fprintf(p_file, "\taddress %s\n", IP4tostr(prtbuf, ipaddr));
-  fprintf(p_file, "\tnetmask %s\n", IP4tostr(prtbuf, netmask));
-  if (!has_pointopoint) {
-fprintf(p_file, "\tnetwork %s\n", IP4tostr(prtbuf, network));
-fprintf(p_file, "\tbroadcast %s\n", IP4tostr(prtbuf, broadcast));
-  } else {
-   fprintf(p_file, "\tpointopoint %s\n", IP4tostr(prtbuf, peer));
-  }
-  if (has_gw) {
-fprintf(p_file, "\tgateway %s\n", IP4tostr(prtbuf, gateway));
-  }
-  fclose(p_file);
+fprintf(p_file, "iface %s inet static\n", netinterface);
+fprintf(p_file, "\taddress %s\n", IP4tostr(prtbuf, ipaddr

Adaptec ATA Raid 2400A and Woody

[George Papamichelakis]

Hello,

I have managed to install woody on a system that uses
the above adaptec card. I had at first to use a minimum
potato installation on a separate disk and then upgrade
to woody, install a 2.4 kernel and then use the dpt_i2o
module to see the raid disk. A friend of mine wishes
to use the same card on a system but he wants to make 
a fresh install directly on the raid device. There aren't
any woody disks with kernel 2.4 as far as I can tell.
Does anybody have a workaround for this ?

George Papamichelakis


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

Re: 3.0.19 show-stoppers

[Stefan Gybas]

On Thu, Jan 24, 2002 at 01:36:37PM +0100, Stefan Gybas wrote:

> I'll make this change in my NMU which fixes the s390 problems.

Testing with current CVS boot-floppies on s390 shows that this section
does not work. It causes dbootstrap to hang after calling debootstrap
(maybe because the cat process isn't properly killed?) and all packages
have been set up. The last message is "I: debootstrap: Successfully
completed" from exec_debootstrap() in extract_base.c - the rest is not
executed:

mkfifo $TARGET/dev/initctl
cat <$TARGET/dev/initctl >/dev/null &
CAT_PID=$!
on_exit "kill $CAT_PID >/dev/null 2>&1"

I'd like to disable this section for the boot-floppies, it's not
necessary there:

if [ -n "$USE_BOOTFLOPPIES_INTERACTION" ]; then
mknod -m 600 $TARGET/dev/initctl p
cat <$TARGET/dev/initctl >/dev/null &
CAT_PID=$!
on_exit "kill $CAT_PID >/dev/null 2>&1"
fi

Any objections? Does the old section work on other architectures?

-- 
Stefan Gybas


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

cvs commit to boot-floppies/scripts/rootdisk by sgybas

[Debian Boot CVS Master]

Repository: boot-floppies/scripts/rootdisk
who:sgybas
time:   Thu Jan 24 05:19:54 PST 2002
Log Message:
  s390 uses devfs, doesn't need devices.tar.gz
  

Files:
changed:SMALL_REMOVE_LIST_s390


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

Re: 3.0.19 show-stoppers

[Stefan Gybas]

On Wed, Jan 23, 2002 at 10:17:11PM -0700, Erik Andersen wrote:

> Umm.  Why not teach debootstrap to use mknod instead?
> There is no good reason for debootstrap to need mkfifo,

I'll make this change in my NMU which fixes the s390 problems.

-- 
Stefan Gybas


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

Re: Things we need from sid

[Chris Halls]

On Thu, Jan 24, 2002 at 07:59:52PM +1100, Herbert Xu wrote:
> I would be happy to do so if someone can show me why we really need 2.4
> boot floppies on i386.  So far, the only reasons I've seen are:
[...]

4. Better network card autodetection support

Its network card was an ISA NE2000 clone.  Using the 2.2 kernel, I could not
tell where the card was configured at, and eventually found a DOS utility
that told me, once I'd got hold of a DOS boot disk.  The 2.4 kernel was
capable of detecting and configuring the card for me without needing any
parameters.  Giving newbies a chance to configure their netcard under 2.4 is
IMO, a big advantage for non-PCI cards.

Chris
-- 
Chris Halls | Frankfurt, Germany



msg15076/pgp0.pgp
Description: PGP signature

Processed: basedebs still not anywhere?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reopen 127546
Bug#127546: boot-floppies: please, please, please include a pointer to basedebs/disks 
somewhere
Bug reopened, originator not changed.

> reassign 127546 boot-floppies
Bug#127546: boot-floppies: please, please, please include a pointer to basedebs/disks 
somewhere
Bug reassigned from package `debootstrap' to `boot-floppies'.

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

[±¤°í] ¹é¸¸ÀåÀÚÀÇ ±æ!!

[e-biz4you]

Title: ¹é¸¸ÀåÀÚÀÇ ±æ



¾È³çÇϼ¼¿ä?
21¼¼±â »õ·Î¿î ±âȸ°¡ ´ç½Å¿¡°Ô ¿Ô½À´Ï´Ù...
°æÁ¦ÀûÀÚÀ¯¿Í ½Ã°£ÀûÀÚÀ¯¸¦ ¿øÇϽʴϱî?´ç½ÅÀ»
¹é¸¸ÀåÀÚ·Î ¸¸µé¾î µå¸³´Ï´Ù. ÇÑǬ¾øÀÌ µ·¹ö´Â ¹æ¹ý. °¡Àå »¡¸® ºÎÀÚ°¡ µÇ´Â
¹æ¹ý. ´ç½ÅÀº ¹é¸¸ÀåÀÚÀÇ ±æÀ» °ÉÀ¸½Ã°Ú½À´Ï±î?¾Æ·¡ »çÀÌÆ®¿¡ ±×ÇØ´äÀÌ
ÀÖ½À´Ï´Ù... 
http://millionaire.kr.kg/
* º» ¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í»çÇ׿¡ ÀÇ°Å [±¤°í]¶ó°í
Ç¥½ÃµÈ ±¤°í¸ÞÀÏÀÔ´Ï´Ù.
* Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»µå·Á Á¤¸» Á˼ÛÇÕ´Ï´Ù. ¿øÄ¡¾ÊÀ¸½Ã´Â Á¤º¸¿´´Ù¸é
Áø½ÉÀ¸·Î °í°³¼÷¿© »ç°úµå¸³´Ï´Ù.
* ´õ ÀÌ»ó ¸ÞÀÏÀ» ¼ö½ÅÇÏ°í ½ÍÁö ¾ÊÀ¸½Ã¸é
[¼ö½Å °ÅºÎ]¸¦ Ŭ¸¯ÇØ ÁֽʽÿÀ.  (¼ö½Å°ÅºÎ¸¦
ÇÏÁö¾ÊÀ¸¼Åµµ ¾ÕÀ¸·Î ÀÌ ¸ÞÀÏÀÌ ´Ù½Ãº¸³»Áö´ÂÀÏÀº ¾øÀ»°ÍÀÔ´Ï´Ù. ºÒÆíÀ» µå·È´Ù¸é ´Ù½ÃÇѹø´õ
±íÀÌ »ç°úµå¸³´Ï´Ù. ÁÁÀºÇÏ·çµÇ½Ê½Ã¿À!)
* ±ÍÇÏÀÇ ¸áÁÖ¼Ò´Â °Ë»ö¿£Áø°ú ¼øÀ§»çÀÌÆ®µîÀ»
ÅëÇÑ ÀÎÅͳݼ­ÇÎÁß¿¡ °ø°³ÀûÀÎ °Ô½ÃÆÇÀ̳ª ¹æ¸í·Ïµî¿¡¼­ ¾Ë°ÔµÇ¾úÀ¸¸ç,¸áÁÖ¼ÒÀÌ¿ÜÀÇ ´Ù¸¥Á¤º¸´Â ÀÏü ¾ËÁö¸øÇÕ´Ï´Ù.




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

Re: Things we need from sid

[Herbert Xu]

Anthony Towns <[EMAIL PROTECTED]> wrote:
>> 
>> kernel-image-2.4.17-bf2.4
>> pcmcia-modules-2.4.17-bf2.4

> So are these an official part of boot-floppies? Should they be being
> (co?)maintained by Herbert to keep them in sync with the other kernels?

I would be happy to do so if someone can show me why we really need 2.4
boot floppies on i386.  So far, the only reasons I've seen are:

1. Support for new hardware.

Without initrd, you can include only so many hardware drivers.  And for all
of the important drivers that I can think of (such as NetGear FA311TX,
AICRAID, Promise Ultra IDE etc.), the support is already in at least one of
the latest 2.2 images anyway.

2. Support for ext3/reiserfs.

IMHO reiserfs simply isn't viable anymore.  So I don't really care
about whether we support it or not.  In any case, there is a 2.2 flavour
available.

Ext3 does not need boot floppies support.  Conversion after installation
of a 2.4 kernel is trivial.

3. Better support for auxiliary hardware such as sound cards.

A 2.4 kernel is only an apt-get install away so this has no place when
we are talking about boot floppies.

If there is another important reason for a 2.4 kernel, please let me know.

Otherwise IMHO this really is unnecessary.
-- 
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]