New answers tagged

0

There are two philosophies of process creation: fork with inheritance, and create with arguments. Unix uses fork, obviously. (OSE, for example, and VMS use the create method.) Unix has MANY inheritable characteristics, and more get added periodically. Via inheritance, these new characteristics can be added WITHOUT CHANGING EXISTING PROGRAMS! Using a ...


1

The distinction between kernel and user (user = non-kernel) is very clear: they have different interfaces, they run in different processor modes, ... Further separations inside the user realm are not so clear. A shell is a program whose job is to run other programs. By this definition, a web server may or may not be a shell depending on what it's used for: ...


0

I am not familiar with Ritchie's layering, but in general you put things into separate layers if one depends on the other. In UNIX/Linux, everything depends on the kernel so it should be in a layer below shell/utilities/server. But web server and shell are mutually independent (mostly, though the shell is needed for service start/stop, too). In general, ...


0

I'm developing on GitHub a function that works just like a HashMap Object, shell_map. In order to create "HashMap instances" this function is able create copies of itself under different names. Each new function copy will have a different $FUNCNAME variable. $FUNCNAME then is used to create a namespace for each Map instance. The map keys are global ...



Top 50 recent answers are included