On 17-Jun-98 Steven Udell wrote:

Marc Bouron wrote:

...

Having now been playing with my newly-installed SuSE 5.2 for a while, I'd like to build my own kernel. Setting the configuration options is one thing, but I'd like to know what they're set to currently: i.e. what does my current (off the CD) kernel look like. Is there any way to tell? Ideally I'd like to be able to build a kernel which is just like my current one, but with a couple of things added (and perhaps a couple of things taken away).

Any hints will be gratefully received.

Well, as a start, take down all the hardware your system has on a piece of paper. So you can have a check list to mark as you are doing the config file of the kernel. [and so on]

However helpful Steven's reply may be about the general procedure for compiling a kernel, it does NOT answer Marc Bouron's question at all. This is the same question I asked several weeks ago, without receiving any reply, not even from the S.u.S.E. team. Namely, to put is in its simplest terms: You install S.u.S.E., and a kernel goes in as part of the installation. QUESTION: What are the configuration settings under which this kernel was compiled? (Or, where may they be found?). Similar if you upgrade -- a new kernel goes in; what are its config data? (And, by the way, it seems to me that this kernel is copied from the boot floppy. This I discovered having found that upgrading, 5.0->5.1, installed the 2.0.32 kernel sources off the CD, while the new kernel that went in was 2.0.33; and that is what I found on the floppy, despite the fact that the label on S.u.S.E.'s floppy said 2.0.32). As well as Marc, I really would like to know the answer to this question! Best wishes to all, Ted. -------------------------------------------------------------------- E-Mail: (Ted Harding) Date: 17-Jun-98 Time: 13:09:44 -------------------------------------------------------------------- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

I don't know if this is really necessary anymore. I have never compiled a.out support into a kernel, and I have never run into a situation where I needed it either. Steven Udell wrote:

a.out binary support (you can do this a module too)

-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Howard Arons wrote:

Now is my chance to ask a question that's been bothering me since I installed 5.2. The kernel I installed out of the box does indeed have SCSI compiled in, but PPP isn't (no boot time PPP message). I have PPP on demand, so I assume that kerneld adds the PPP module as required. If so (a big if for a Linux newbie), why did you recommend that PPP be directly compiled?

Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Netscape 4.0

Thank you, Howard. I was "corrected" a week or so ago for stating the 5.2 "out-of-the-box" kernel didn't have PPP compiled in. -- Ken Schuller Network Support Specialist NovaNET Learning, Inc. <hint> Take out the spam foil to reply via e-mail. </hint> Incidentally, I speak for me. That's all. No one else. Linux- the best things in life are free! (Or at least GPL'ed...) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hi! Trying to kill the keyboard, hettar@teleport.com produced:

Well whats cool it that you can do make menuconfig as many times as you like and spend all day looking at it, learning and reading the help on each thing you can add to the kernel.

And there's xconfig, too :) But as a beginner you'd better start X as root (or log into xdm as root), cause else you'd have to tell the thing to use your xserver (export DISPLAY=localhost:0.0 as root) and tell the server to allow it (xhost + localhost as the user who started it).

Just try not to bloat your kernel with things you will never use nor need.

exactly. And always have a backup kernel that works.

things to note: SCSI should be compiled directly

... if you have SCSI disks and use them, especially if your / is on SCSI. If you are on (E)IDE and have a SCSI-CDROM or ZIP or something, leave it as modules. (remember, you need SCSI-Support, support for the type (i.e. Disk) and support for the Adapter, too.)

filesystems can be mounted mostly as modules too

but not ext2, cause you need that for your / (unless you have an UMSDOS system :-) so you can get the modules.

a.out binary support (you can do this a module too)

Does not hurt as a module.

ppp should be direct compiled too

Nope. Works perfectly as module.

Thing about todays Kernels is they are hightly moduleized (or can be) for sleek,quickness, and non bloat.

... so put everything you need not 990f the time as module, if you can (and are allowed, see ext2). -Wolfgang -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e