Re: impressions of a new user

On Fri, 15 Aug 2003, Ben Goren wrote:

> > Why not make OpenBSD as consistent and approachable an OS as possible?

> Here's your chance: provide that ``more reasonable''

> http://www.trumpetpower.com/pub/.profile

Well, let's start with the basics.

All three files in (/etc/csh.cshrc /etc/csh.login /etc/csh.logout) are empty by default. Make /etc/profile an empty file in the same way, if you at least don't want to do this:

        PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/games

	if [ Xroot = X"$USER" ]
	then
		PATH=/sbin:/usr/sbin:$PATH
	fi
	export PATH

	HISTFILE=.sh_history

	TMOUT=600

	umask 022

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

The above items enhance security. I can imagine no objection to their inclusion.

/etc/skel contains two csh configuration files (.cshrc .login). These files configure terminal settings, set this shell history file, set the prompt, set the umask, and configure defaults for ex/vi (and they are redundant in a few places). /etc/skel/.profile does none of this.

The same sorts of things should be done for ksh that are done for csh. How can you claim consistency when the environments are totally different?

   / Charles J. Fisher              | "A fanatic is one who can't change his /
  /  cfisher@rhadmin.org            |  mind and won't change the subject."  /
 /   
http://rhadmin.org             |                 -- Winston Churchill /
---------------------------------------------------------------------------