Complete.Org: Mailing Lists: Archives: local: February 2002:
[aclug-local] Re: Suggestions: Next Meeting

[aclug-local] Re: Suggestions: Next Meeting

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: local@xxxxxxxxx
Subject: [aclug-local] Re: Suggestions: Next Meeting
From: "James G ." <jamesga@xxxxxxxxxxx>
Date: Tue, 12 Feb 2002 11:51:01 -0600
Reply-to: local@xxxxxxxxx

Yes, exactly (rc.d, lilo, etc.). Except I meant to say boot-up "sequence". 
That word did not roll off my tongue properly.

It seems that when we are trying to form ideas, people tend to jump to 
conclusions and and add meaning to things that are not intended (intead of 
clarifying and looking at the whole picture). 
Also, I think what got decided on yesterday was very good. After beaking 
the organization into different parts, we can now better decide how to 
deal with people new to GNU/Linux. Each portion of the group can decide on 
how best to manage this issue individually. I also hope that this issue 
(new users) will no longer be ignored.

Your friend,
James Galimi

On 2002.02.12 11:12 bbales wrote:
> On Monday 11 February 2002 04:40 pm, James G. wrote:
> > Anyway, at the last meeting, I mentioned we should include a talk on
> how
> > Linux boots up. Someone else (not me) translated that to mean I wanted
> to
> > dissect the Linux kernel. No No No. Boot-up scripting steps is
> different
> > than understanding the kernel.
> OK, James,  Maybe I understand what you are saying.  Is this it?
> During bootup, what programs are called and  _BASICALLY_ what do they do?
> LILO, inetd, initd, rc.d and rc3.d, and many other programs.   How is
> grubb
> different from LILO?  How do the various *.conf files play with the other
> files?  What gets put into dmesg and why?
> Is this close to what you were asking for?  If it is, I would like to see
> this myself.
> bruce

[Prev in Thread] Current Thread [Next in Thread]