On Llu, 2006-01-09 at 17:53 +0100, Oliver Neukum wrote: > Does the Windows Explorer draw icons based only on name and metadata? Sort of. It also plays tricks on the human by working out what icons are visible and loading those first then filling in while the user thinks it is ready - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: "Jeff V. Merkey" <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: Oliver Neukum <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: Lee Revell <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- References:
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: Bernd Petrovitsch <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: Lee Revell <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- From: Oliver Neukum <[email protected]>
- Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- Prev by Date: Re: [PATCH] ia64: including <asm/signal.h> alone causes compilation errors
- Next by Date: Re: [OT] ATI 64-bit fglrx compile patches for 2.6.15-gitX
- Previous by thread: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- Next by thread: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
- Index(es):
 |