On Thu, 26 Mar 1998, Bradley, Greg wrote:
[...]
init--which isn't part of the kernel--doesn't exist
Here we have a perfect example of an OS asking requiring user input.
Huh? When does init ask for user input? How is the "OS" asking for
input when dealing with init?
[...]
Without all of this,
For instance, under your definition for the Linux "operating system",
the system could
not communicate with the network
It is not necessary to have a NOS to have an OS. We had stand alone
mainframes
with OS's before lans were invented.
/bin/sh--which isn't a part of the kernel
I don't have
How? The kernel starts init (
Before we can load the kernel, we need a bootstrap in the bios. Is this
part of the
operating system as well?
Huh?
The program, init, is a user input. Put a different program there called
init and something
different happens, according the the users input, ie the
Huh? When does init ask for user input? How is the "OS" asking for
input when dealing with init?
init INPUTS a SCRIPT file, /etc/init.tab containing instructions FROM
THE USER (root) on what to do.
Functionally this is the same as dos reading autoexec.bat.
If you have a standalone Linux
On Thu, 26 Mar 1998, Steve "Stevers!" Coile wrote:
Huh? When does init ask for user input? How is the "OS" asking for
input when dealing with init?
Init accepts arguments these are inputs aren't they. I might not
understand init very well but I thought that you need to define for init
what
After you boot the kernel, you can run any number of PROGRAMS to provide
the functionality required,
getty, bash etc might be useful here. The act of running the program is
an acceptance of user input.
The kernel manages memory and autoboots, so it handles peripherals.
ergo, it is an operating
