[buug] login [not] a daemon? ... & CDs

Karen Hogoboom khogoboom at gmail.com
Thu Mar 10 06:30:13 PST 2011

The machine gets power.  Memories of gears turn.  Eventually the bios starts
(on my Dell).  The kernel gets invoked.  In system memory, input from the
console gets put into a system buffer.  It overflows or the code is good.
Eventually rc.d gets read?  Then there's an exec?

Thank you Ian and Michael for the clarification up to this point.

I still don't see why a base install of BSD decided I wanted to use PAM.


On Thu, Dec 2, 2010 at 5:58 PM, Michael Paoli <
Michael.Paoli at cal.berkeley.edu> wrote:

> From: "Ian Zimmerman" <itz at buug.org>
>> Subject: Re: [buug] hello
>> Date: Thu, 02 Dec 2010 08:36:32 -0800
>  Karen> That is my new project for awhile then.  login [pam] -- I fail.
>> Karen> I don't know why there has to be a daemon for login.
>> Not a daemon.  This is the same process that becomes your shell after
>> you log in.
> Well, ... depends a bit how one logs in, ... may or may not *directly* be
> a daemon, ... but there would at least be inetd or xinetd or init somewhere
> behind it ... it nothing else.  Has to be something that forks/execs that
> shell or login/shell/process.
> ... 1 hr. to BUUG :-) ... oh, and I'll be bringing some CDs (Ubuntu &
> others).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buug.org/pipermail/buug/attachments/20110310/65b32181/attachment.html>

More information about the buug mailing list