Path: utzoo!attcan!uunet!samsung!usc!ucsd!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.unix.wizards
Subject: Re: time dependent login
Message-ID: <1990Jun11.154010.7363@iwarp.intel.com>
Date: 11 Jun 90 15:40:10 GMT
References: <1990Jun6.081403.10065@hawkmoon.MN.ORG> <234@rossignol.Princeton.EDU>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 27
In-Reply-To: tr@samadams.princeton.edu (Tom Reingold)

In article <234@rossignol.Princeton.EDU>, tr@samadams (Tom Reingold) writes:
| In article <1990Jun6.081403.10065@hawkmoon.MN.ORG> det@hawkmoon.MN.ORG
| (Derek E. Terveer) writes:
| 
| $ On sun os systems, which are bsd derivitives, if a user attempts to login
| $ without a home directory, they *are* allowed to login and are plopped into
| $ "/", i.e., root.
| 
| That's not the point.  I think you are responding to someone whose
| suggestion was to make the home directory owned by root and
| *unreadable* and *unwritable* to the user.  The question is, would
| *this* prevent a login?

I think <det> answered that, as in "it wouldn't matter".  If you
cannot cd to your home directory (as denoted in /etc/passwd), you get
"/".  If you *can* cd there, it doesn't matter that you cannot read
it.  I can spend *weeks* logged in without ever writing into my home
directory, so making it unreadable and unwritable is ineffective.  If
necessary, I'd just "setenv HOME /tmp", to keep the programs that want
to write into the home directory happy.

Just another UNIX hacker,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/