nrh (08/09/82)
This setuid stuff is getting silly! Why fix something that works fine? Oh sure, you lose your c-shell history, but if that's a problem, fix things there. Wouldn't it be nice if you could log in and find your previous history in place?
idallen (08/10/82)
"Wouldn't it be wonderful if you could log in and find your previous history in place?" -- esquire.381 (nrh) Wonderful! Bravo! Yes! That's exactly the right train of thought. Just take it a little farther. I've had my directory stack saved and restored over logout/login for months now. I want more! You know what this is leading to? Don't go half-way -- why log in or out at all? Who ever came up with the concept of "logging in" and executing a profile? Why do all my aliases go away, my directory stack, my history list, my background processes? When I log out, save EVERYTHING that's reasonable to save. When I log back in, restore it. No wasting time re-loading my CSH shell from a .cshrc, just save the core image of the shell and reload it when I log back on! I've done this sort of thing (as best I could) on our Honeywell GCOS timesharing system since 1977. I may try it here on UNIX some day. What good is login/logout anyway? -IAN! U of Waterloo (decvax!watmath!idallen)