From: Joshua Hudson (joshudson@hotmail.com)
Date: Mon May 21 2001 - 23:56:59 CEST
Michele Andreoli wrote:
>On Mon, May 21, 2001 at 09:31:59AM -0700, Joshua Hudson nicely wrote:
> > I am interested in developing new shell for muLinux (believe I can >
>beat ash
> > for size & speed). In attempting to determine what happens in login, I
> > could not get output to the screen. The same thing happens with
>programs
> > being used as login shells, like so:
> >
> > This is the entry I added to /etc/passwd:
> >
> > who::103:100:Dr. Who:/:/usr/bin/who
> >
> > The result in logging in (minus /etc/issue):
> >
> > muLinux login: who
> >
> > muLinux login:
> >
> > The error is in init or agetty: running login from the command line
> > works just fine:
> >
> > # login
> > muLinux login: who
> > who tty0 (rest of output deleted)
> > #
> > _________________________________________________________________
>First of all: we have two "login" program: the fake/rustic one /bin/login,
>and GNU login in /usr/srv/bin/login. The second take place only if
>you load the SRV addon.
>So, /bin/login acts as wrapper: in the case SRV is not in memory, it
>simply call "ash".
>As you surely guessed it, the rustic login do not inspect the
>/etc/passwd, so check what really happens in your case.
Michele
My muLinux system is ROOT + USR + SRV + GCC cloned on a harddisk, so
/usr/srv/bin/login is availiable
I was hoping you would know why it does this so my shell can accomodate.
Is the terminal-opening code in /bin/ash?
To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.dk
For additional commands, e-mail: mulinux-help@sunsite.dk
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.dk
For additional commands, e-mail: mulinux-help@sunsite.dk
This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:19 CET