Editor With NO Shell Access?
freebsd at edvax.de
Tue Mar 13 00:14:20 UTC 2012
On Mon, 12 Mar 2012 16:34:18 -0700, Edward M. wrote:
> On 03/12/2012 03:47 PM, Edward M. wrote:
> > On 03/12/2012 03:23 PM, Polytropon wrote:
> >> On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
> >>> On 03/12/2012 03:10 PM, Polytropon wrote:
> >>>> /etc/shells to work, but a passwd entry like
> >>>> bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
> >>> I think this would not let the user to login,etc
> >> I'm not sure... I assume logging in is handled by /usr/bin/login,
> >> and control is then (i. e. after successful login) transferred
> >> to the login shell, which is the program specified in the
> >> "shell" field (see "man 5 passwd") of /etc/passwd. How is
> >> login supposed to know if the program specified in this
> >> field is actually a dialog shell?
> >> From "man 1 login" I read that many shells have a built-in
> >> login command, but /usr/bin/login is the system's default
> >> binary for this purpose if the "shell" (quotes deserved if
> >> it is an editor as shown in my assumption) has no capability
> >> of performing a login.
> > Now i gotta try this out. Off to
> > hosed my system.
> Does not work. Could not login, it shows "Couldn't open *-joerc."
Very strange message. I know there's a .joerc in ~ (for the
user) and a global /usr/local/etc/joe/rjoerc (for system-wide
I also get this message:
Couldn't open '*-joerc'
Maybe this is because joe isn't a shell and doesn't set some
required variables, such as $PATH or $HOME, and joe cannot
find its rc files...
The reason is what I see in /usr/ports/editors/joe/work/joe-3.7/main.c
line 353 and above.
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions