Hi folks. I said a while ago I intended to change how various files needed by M5 were located, and this weekend I started looking into actually doing that. The first thing I think I'm going to do is keep the end behavior basically the same but adjust how SysPaths.py works to make it more amenable to the what I want to do and to clean it up a bit. Looking at what it does now, there are two paths that are used if the M5_PATH environment variable isn't set, "/dist/m5/system" and "/n/poolfs/z/dist/m5/system".
The later of these is obviously to make running things on the cluster at UM easier, and isn't useful to anyone not in a position to do that (or even some of us who are). I propose we eliminate that path outright and adjust any scripts that, for instance, run the regressions to set M5_PATH explicitly. The former path I'm less sure about. We've always had stuff in /dist since I've been involved with M5 and I've always just taken it for granted, but where did that actually come from? Why do we put things there? I've started digging around various interpretations of what a Linux file system should look like trying to find a more standard location, but I haven't found anything that's obviously the right place. I've seen no mention of /dist, though, so it seems even more odd now. Is /dist something we could reasonably expect people to already have or to not be too put out to create? Or do we want to pick somewhere less unusual? Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
