Introducing /run

Posted Mar 30, 2011 22:59 UTC (Wed) by dskoll (subscriber, #1630)
In reply to: Introducing /run by martinfick
Parent article: Introducing /run

I hate the occasional times I have to use a Windoze box and deal with monstrosities like C:\Program Files\Some Stupid Vendor Name\Some Huge Directory Name

And in my (mercifully) brief encounter with Mac OS X, I was similarly disgusted by its reworking of the standard UNIX directory layout into a verbose user-friendly [sic] horror.

to post comments

Introducing /run

Posted Mar 31, 2011 6:04 UTC (Thu) by frazier (guest, #3060) [Link] (1 responses)

In MS Windows, I end up using "C:\progra~1\" in my paths more often than I'd like to admit to.

Introducing /run

Posted Mar 31, 2011 16:40 UTC (Thu) by zlynx (guest, #2285) [Link]

You don't open up cmd and run fsutil immediately after a fresh Windows install and speed tweak all the options?

You've got to make sure TRIM is on and 8.3 names are off and last-accessed is off and you might like to tweak the memory buffers if you've got gobs of RAM.

With 8.3 names off, C:\program~1 fails to work, but at least NT stops reminding me of DOS.