On Tue, 10 Apr 2001 [EMAIL PROTECTED] wrote:

> One thing I have to know: is there already a patch for ext3 to the
> 2.4.x series?  I know it's not already in 2.4.3.  I would have wanted to
> convert the root partition on my laptop to ext3 in case the s--t for
> brains people who sometimes use it for its windows partition mistakenly
> boot Linux.  Migrating back to 2.2.19 is not an option for me, because
> none of the USB devices I own have support in the 2.2.19 USB backport. 
> Reiserfs requires a full reinstall if I want to put it on my root (and
> only) partition, and that's not something I can bear to think about
> right now...

>From the ext3-faq (http://people.spoiled.org/jha/ext3-faq.html)

Q: Is there/ will there be a patch against Kernel 2.4.0?

Stephen C. Tweedie's answer: 
"There will be, and I'll be working on it soon." 

In the announce mail for 0.0.5e Stephen wrote about his plans:
"I want to move to a freeze of this development code a week or so after
0.0.6. I'll move to a 0.9 numbering at that point to indicate that this is
to be stabilised for an ext3-1.0 as soon as possible, which means
basically that as much testing as possible would be appreciated, so I'll
be doing RPMs for the kernel as of 0.0.6." 
---SNIP--- 
"The plan is to go to a kernel-style numbering scheme once we have
codefreeze: 0.9 will be the codefreeze for a 1.0 release, but I'll fork a
1.1 branch for developments such as a 2.4 port while 1.0 is kept stable
and supported as the baseline 2.2 version."
<eoq>

what USB devices do you have that don't have a backport?

___ eric pareja ([EMAIL PROTECTED]) ~-=[O]=-~ Here, have a clue. Get the picture.
\@/ PGP key at http://gra.ph/~xenos/xenos.pgp <|PLUG|> http://gra.ph
 v  "Any technology distinguishable from magic is insufficiently advanced."  
    - Emperor Cleon in "Foundation's Fear" by Gregory Benford

_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
[EMAIL PROTECTED]

Reply via email to