cvs commit: src/sys/dev/ata ata-queue.c

[Scott Long]

Warner Losh wrote:
>>The discussion started with des saying something like "the classic way is
>>bad, don't do this" while it would have been enough to say "and with the new
>>procedure it looks like". I don't want to pick on des here, everyone can have
>>a bad day. But he isn't the only one, in the past I've seen alot of people
>>pointing their gun at someone who uses the classic way and pulling the
>>trigger, and I don't think this is OK.
> 
> 
> OK.  The classic method will likely work forever, where 'work' is
> narrowly defined as "if your system is compatible enough" which most
> developers know.  There's too much momentum...  I for one only use the
> new method for upgrades, and as part of product release scripts.
> 
> 
>>Let's shut up now and maybe put a sentence or two about KODIR and nextboot
>>into the updating description.
> 
> 
> Sounds good to me.
> 
> Warner

Where the traditional method is immensely useful is in customizing your 
kernel immediately after doing a fresh install from CD/ftp/floppy.  You
want a slimmer kernel right away without having to suffer through doing
a buildworld.  This is even more true on 6-CURRENT snapshots where 
INVARIANTS and WITNESS are enabled and really slow things down.  There 
is simply no need to do a buildworld, since your sources are completely
in sync with the system.  I appreciate the effort that has happened over
the years to make the whole upgrade process smoother, but we can't
define 'work' too narrowly or else it becomes just as cumbersome as the
problems that we are trying to fix.

Scott