Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Why is it that Linux is command based and Windows is GUI based

Status
Not open for further replies.
I do not accept the premise of the question! Whatever the GUI experience is, in either system, contriving mouse clicks to be the alias for a command string is something they all have. Even now, however deeply the command is buried in a GUI experience, one can still find a place where the command can be seen.

.. and if the keyboard is your friend, here is another possibility for command line entry and scripting:

https://en.wikipedia.org/wiki/Windows_PowerShell
 

It seems my last reply did not leave any impression upon my friends,
specially the post starter. Anyway, if we analyze more specifically, it may be
said that during three layers of processing that is user, supervisor and
hypervisor lies the answer as follows :
For example for windows,
1) User>
{any app>middleware or windows app(API)}
2) Supervisor>
{WinXP-fully virtualized subject(win-32 API-virtual
CSP-BSP-Drivers>subject}
3) Hypervisor
{kernel>Hardware}.

Similarly, for Linux,
1) User>
{any app>middleware or Linux app(GLIBC)}
2) Supervisor>
{Linux/SE Linux(Open-standards API-virtual CSP-BSP-Drivers>subject}
3) Hypervisor
{kernel>Hardware}.
 
Last edited:

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top