>>>>> "Edward" == Edward Ned Harvey <lo...@nedharvey.com> writes:
>> So any stardard is going to break no matter what you do. Which is why >> I liked the Lucent one. There was no standard name, which meant no >> standard expecations to break. Edward> The only thing I didn't like about the lucent one was ... at Edward> first, the name was chosen by HR. Well I must admit that the hiring manager did have some influence on this process, but by default HR would pick one if no preference was indicated. Edward> The naming convention I use for my users is: User chooses Edward> their username, which must be unambiguously based on their Edward> real name, and max 8 characters. This way, you can see any Edward> file owned by jsmith, and you'll unambiguously know it belongs Edward> to John. What about James? Or Julie? or Julio or Juan or Javier? Where do they all fit into the grand scheme of things. Go look through the phone book of your town and see how many names are the same. How do you disambiguate them? Edward> Users are all coming from somewhere, and they prefer to have Edward> the same username at different locations. So why should I be Edward> eharvey at one company, and harveyed at some other company? Yup, deal. I've been: john, jfs, john, jstoffel, stoffel, stoffj in my career, that's just counting Unix systems. Sometimes Unix and Windows weren't kept in sync in the same company which led to all kinds of hell... No matter what scheme you come up with, it MUST address and understand and handle gracefully name conflicts. This is why I feel that the Lucent (though I bash them on lots of other stuff!) handle scheme was so nice and scalable. It basically said: conflicts occur, there is no standard beyond keeping it not-rude. We had one engineer who's handle was 'boingy' or something like that. Had a perfectly fine first and last name, but went by this pretty much everywhere. John _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
