Andre Hedrick wrote:
>
> Is this the first sounding for a ./drivers/legacy/**
>
> A place to store retired coded that would need to be maintained, but on a
> limited bases?
I don't think so. Just toss it like ext1 and xiafs. The question is
when to do so, and this would be assessed on an individual driver basis.
Some things (like xd.c) could be tossed now but I would suggest a
list of drivers/code be lined up for a cull for 2.5.0
Think about it - allow up to a couple months before 2.4.0 becomes
a reality, and a lifespan of at least 1.5 years for 2.4.x as the
`current' kernel. Thus things marked for death in early 2.5 will still
be supported approximately 2 years from now regardless.
> I wish you had spoken up earlier.....
> I just booted "hd.c" and it is a brick! FSCKing a 13GB with "hd.c" DON'T!
Of course. "hd.c" is essentially unchanged since v1.0.9 - you wouldn't
try to saturate a 100Mbps network with the v1.0.9 stack either. The best
ST506 MFM controller (1:1) maxes out at about 460kB/s. 16 bit ISA IDE
cards and early drives shipped with them were typically good for only
about 1.2 MB/s. So hd.c is not a bottleneck for its intended applications.
Paul.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:24 EST