s887212@minyos.xx.rmit.oz.au (Stephen Riehm [Romulis]) (11/16/90)
were does one find descriptions for '.' files? I have long known of the existence of 'dot' files, ie .cshrc .login etc however I have NEVER come across any documentation on how to use these or any mention of what dot files are available to do what. So far these are the dot files that I know of... most I picked up by word of mouth and the .exrc .cshrc .newsrc .login and .logout are the only ones I really understand. .cshrc .exrc .hushlogin .login .logout .mailrc .newsrc .rhosts .twmrc I have heard of many more.. .profile comes to mind but I don't know what should go in them etc etc. Is there a complete list of "common" user definable dot files available.. failing this if anyone knows of the name and format of a file to Ignore mail from a user I would be very grateful. thanx in advance ============================================================================ Romulis [Stephen Riehm] Royal Melbourne Institute of Technology, (124 Latrobe St., Melbourne.) s887212@minyos.xx.rmit.oz.au Australia. ELM, X, VI, UNIX : these things make life bearable. NN: makes life LIVABLE! ======================< Insert Usual Disclaimer >===========================
weimer@ssd.kodak.com (Gary Weimer) (11/16/90)
In article <6270@minyos.xx.rmit.oz.au> s887212@minyos.xx.rmit.oz.au (Stephen Riehm [Romulis]) writes: > >were does one find descriptions for '.' files? > >I have long known of the existence of 'dot' files, ie .cshrc .login etc >however I have NEVER come across any documentation on how to use these or >any mention of what dot files are available to do what. >So far these are the dot files that I know of... most I picked up by word >of mouth and the .exrc .cshrc .newsrc .login and .logout are the only ones >I really understand. >.cshrc .exrc .hushlogin .login .logout >.mailrc .newsrc .rhosts .twmrc > >I have heard of many more.. .profile comes to mind but I don't know what >should go in them etc etc. >Is there a complete list of "common" user definable dot files available.. 'dot files' do not have any meaning in and of themselves. They are only important to the programs that use them. Notice that many of the files end in 'rc' (anyone no the meaning of this? I'm sure it's related to the rc in /etc/rc & /etc/rc.local). These are initialization files for the named program. The meaning and format of most of these files can be discovered by doing a man on the file name minus the '.' and 'rc' (i.e. for '.mailrc' do a 'man mail'). If the dot file does not have an 'rc', try doing a man on the whole file (i.e. for '.rhosts' do a 'man rhosts'). If neither of these work, try doing a man on a recognizable part of the file name (i.e. for '.hushlogin' do a 'man login'). If you haven't found it yet, try doing keyword searches using the above algorithms (i.e. 'man -k mail' 'man -k rhosts' 'man -k login') If none of these work (like for .profile), ask someone else (like here). The ones I know: .cshrc -- commands to execute when starting csh(1) .hushlogin -- suppress the message of the day when logging in .login -- commands to execute when loggin in (see "Initialization & Termination" in csh(1)) .logout -- same as .login, but done at logout, not login .profile -- the equivalant of .cshrc for the bourne shell (sh(1)) .rhosts -- list of remote hosts (see rhosts(5)) .twmrc -- initialization for twm (X window manager) .exrc -- ' ' '' ex (editor) .mailrc -- ' ' '' mail (the obvious) .newsrc -- ' ' '' news (rn on my system) Hope this helps. Gary Weimer
rob@b15.INGR.COM (Rob Lemley) (11/30/90)
In <1990Nov16.141503.5567@ssd.kodak.com> weimer@ssd.kodak.com (Gary Weimer) writes: >In article <6270@minyos.xx.rmit.oz.au> s887212@minyos.xx.rmit.oz.au (Stephen Riehm [Romulis]) writes: >> >>were does one find descriptions for '.' files? >> >'dot files' do not have any meaning in and of themselves. They are only >important to the programs that use them. >Notice that many of the files end in 'rc' (anyone no the meaning of this? The rc stands for "runcom" or "run commands." I believe that this convention came from an operating system which predated Unix. Rob Lemley
hamilton@kickapoo.cs.iastate.edu (Jon Hamilton) (12/02/90)
rob@b15.INGR.COM (Rob Lemley) writes: >In <1990Nov16.141503.5567@ssd.kodak.com> weimer@ssd.kodak.com (Gary Weimer) writes: >>In article <6270@minyos.xx.rmit.oz.au> s887212@minyos.xx.rmit.oz.au (Stephen Riehm [Romulis]) writes: >>> >>>were does one find descriptions for '.' files? >>> >>'dot files' do not have any meaning in and of themselves. They are only >>important to the programs that use them. >>Notice that many of the files end in 'rc' (anyone no the meaning of this? >The rc stands for "runcom" or "run commands." >I believe that this convention came from an operating system which >predated Unix. Um, actually, I believe .rc stands for "runtime configuration" - but I've been wrong once or twice before. :) jon hamilton >Rob Lemley
friedl@mtndew.Tustin.CA.US (Stephen J. Friedl) (12/02/90)
In article <1808@b15.INGR.COM>, rob@b15.INGR.COM (Rob Lemley) writes: > > I believe that this convention came from an operating system which > predated Unix. You're telling us that there was actually life *before* UNIX? Steve :-) -- Stephen J. Friedl, KA8CMY / 3B2-kind-of-guy / Tustin, CA / 3B2-kind-of-guy +1 714 544 6561 / friedl@mtndew.Tustin.CA.US / {uunet,attmail}!mtndew!friedl "If it doesn't core dump, ship it" - Gary W. Keefe, on product development