🚀 go-pugleaf

In article <danpop.827809042@rscernix> danpop@mail.cern.ch (Dan Pop) writes:
>In <4j6lv1$k3r@news.mpd.tandem.com> Joseph Crowe <jcrowe> writes:
>
>>danpop@mail.cern.ch (Dan Pop) wrote:
>>>Can you use a Unix system without a shell?  Try to remove all the shells
>>>from your Unix system and see what you get :-)
>>
>>   Absolutely.  You could have a user login on a *NIX system and in the
>>/etc/passwd entry for that user, have whatever binary you wish to provide the
>>user interface.  That could include a totally graphical interface if one so
>>desired.
>
>Your Unix system won't even boot without a shell!  Just remove all the
>shells, as I suggested and see if you can use that box, no matter what
>you put in /etc/passwd as the user login shell.

You have NO idea what you are talking about!

>
>The shells (or at least /bin/sh) are part of the design of a Unix system.
>Library calls like system() and popen() or system components like cron
>rely on the existence of /bin/sh and simply don't work without it.

cron uses a shell to SIMPLIFY things!  Don't you need to have lotus 1-2-3 to
have full 1-2-3 functionality?  HUH??????


system means "send command to SHELL"!!!!!!!
popen means "open a SHELL and use a pipe for terminal I/O"!!!!!!!
cron means "send a command to the SHELL at a particular time"

NOW HOW do you send a command to a shell without having the shell, HUH?



>>>BTW, you found no contradiction:  Will Packard is perfectly right, Unix
>>>is not one or more shells, for the simple reason that the shells are a
>>>component of the Unix system.  The other components are the kernel and
>>>the system utilities.  All these components define a Unix system.
>>
>>   Shells in *NIX are applications, pure and simple.  
>
>True, but irrelevant.  Everything in Unix is an application.  Some of them,
>(e.g. /bin/sh, getty, login, init, ifconfig) are critical components of 
>the operating system.

I don't believe I have EVER used sh here!  I am planning on getting rid of 
getty, and have in the past!  

Let me set you straight, ok???  UNIX is TRULY only a multitasking system which
has all things running at a high level.  init manages tasks, or which one is
getty.  getty simply waits for a signal to start login.  login starts the
shell(which could be ANY program)!  

ifconfig?  That is simply for NETWORKS!  Are you telling me the macintosh has
NO ability to configure networks?


>
>>They are forked from the
>>login process based on the entry in /etc/passwd for whatever user is logging
>>in. 
>
>You don't have too many clues about Unix, do you?  There are tens if not
>hundreds of shell processes started during the booting procedure, before
>the first login prompt is even displayed.  After the kernel has been 
>loaded and the init process has been started, everything else is done
>by shell scripts.
>
>>In many installations, certain logins will cause the fork()ing and
>>exec()ing of some sort of window oriented application.  The *NIX OS is
>>basically the kernel and system call interfaces, plus perhaps, libraries.  Not
>>that this has a whole lot of relevence.
>
>Plain bullshit.  Remove all the system utilities from /bin /usr/bin /sbin
>/usr/sbin, etc and see what you can do on that Unix system.  After all,
>you still have the kernel and the libraries.

Try removing all the system files on the MACINTOSH, and see how far you get!