Re: and yet another zdnet "article" re: Lnx

[johnhazel@xxxxxxxxxxxxx]

On Thu, 14 June 2001, Dirk Bartley wrote:

> Which brings me to the projects making an effort to gui-fy Linux.  I'm all for
> it.  However, they really ought to tell you what text/configuration files it is
> editing when they do it.  A big difference to me between Linux and MS is that
> windows is a mystery, Linux is an open book.  I'd like the new people trying to
> use Linux see the book through gui.  Lets say I'm in Linuxconf and I just
> changed something in sendmail.  I would really like it if it told me what file
> it changed what the original file was renamed to and give me the option to see a
> result of a diff command between the two. 

To the eyes of one hopeful Linux user (me) this looks like an excellent idea. Having a GUI (a.k.a. crutch, leash, nose ring) yet being able to peek over the GUI blinders and into the system would be extreemly helpful. It would spark small bits of understanding that would help me to see the whole picture better. 

> They also could have more
> explanations.  Assume you don't understand something, url to an explanation on
> the web somewhere. 

I would like to have an ultra-verbose install kit. One that replaces the cute graphics and messages with serious detailed explanations in a step by step manner. This install would take 1-4 weeks but I can't imagine a faster way to detailed understanding of the OS. 
The initial screen would allow the user to choose ultra or normal verbosity during istall. After choosing "ultra" the next screen would start from the very beginning. "When power is first applied to a microprossesor (uP) it looks at a hardwired address for it's first instruction, The BIOS is wired to provide this first instruction. .... The BIOS instructions tell the uP to test memory by writing and reading at each memory location. As each kilobyte is completed the uP sends a update to the screen buffer....at the end of the BIOS execution phase, the BIOS starts the first instruction of the OS by sending..." Each installed component of the OS would be explained at the BUS-uP I/O level of functionality untill an absolute minimum system is established. This would be a command line state where the user would be able to look around in the bare bones setup on the hard drive and also the install CD. Next the user would need to transfer a few packages from CD to HD and manually issue commands to install them. Maybe a display driver and a little(big?) utility to show the state of the computer. (memory map, file structure and files). Each major function would be added manually 
The user could issue the command line "memmap" and a graphic (made possible by the utility and screen driver install) would show the memory configuration and use.

I have tried to set up a minimum LINUX sytem equivalent to the DOS command line before and had no luck because I am so lacking in OS knowledge. This problem is clearly (to me) a result of not being allowed to look through the Windows on my computer.....

> I know what your thinking, Join the linuxconf team then.  OK
> I'm a hypocrite.

Well there is some protection from the masses that must exist for the leaders in any large organization to allow progress by those leaders.  
Joining a group of leaders like "linxconf" or "kernelcrackers" with the goal of learing basics is doing the whole community an injustice.
A system as I described above and/or a university or high scool course developed as the "ultra verbosity" would be a great service to all concerned. 
The advantage of the course would be that the instructor could select the machine to install on. (cheap, if you use the ones that were replaced in the computer lab). 

John Hazel

Liftroll is at: http://www.geocities.com/jebbushell/COOKBOOK.htm 
Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com