ippp, ppa, ramdisk (i.e., parameters for kernel compilation)
Dear Debianers,
I am about to try my first kernel compilation after a successful
installation of Debian 2.0.
I have a couple of questions, the former not related to the kernel
itself.
1) While selecting/installing isdnutils, I was prompted to enter the
name of whatever (I did not know what that was) and the message
ended with (ippp0 ippp1 ippp2 ...):
I typed ippp0. Afterwards, I got the message that
/etc/isdn/ipppd.ippp0 is not yet configured. I thought this was all
right since I haven't bought an ISDN card yet and some configuration
must be done by hand (as for gpm, I think), by editing a file.
However, at reboot I also see a new message saying
INIT: /etc/inittab[74]: id field too long (max 4 characters).
Is this a problem with that name ipppd.ippp0 or something else?
2) I'll have to choose kernel compilation options: I am working on an
IBM Thinkpad which will be connected to the rest of the world only
via an ethernet PCMCIA card and an ISDN card, no printer. Do I need
ppa (i.e., something I think is related with the parallel port)?
The boot message about ppa currently says: SPP present, EPP not
supported, probing 03bc, 0378, 0278 ...
3) Presently, I also get the message:
RAMDISK driver: 16 ramdisks of 4096k size.
I do not know what a ramdisk is (although I can imagine it): do
I need any of them, is that a compilation option?
I have a 2.1 GB HD, 40 MB ram (probably 64 in the future), and a 40MB
Swap partition (just in case this is relevant to the ramdisk choice).
4) At boot time, I also get the message
Unable to load NLS charset cp437 (nls_cp437): again, I do not know
what that is, but the file is on the disk, together with several
other ones with analogous names.
5) Finally, kernel-package allegedly makes things easy. If I understand
correctly, I am supposed to rename the directory /etc/modules/2.0.34
to something else since that gets overwritten. Is all the rest
automatic? Where does the new image "go", so that I can correctly
point to it in the new lilo.conf? A sample lilo.conf with the call
to the original kernel and to a custom-made one would be helpful.
I do not see any "fakeroot" on the disk: is the command in the
documentation correct? It ends in kernel-image: do I have to type
"kernel-image" or a fantasy name for the image to be created?
THis is not clear from the README file.
Of course, I am going to finish reading the documentation in the
meantime, but any clarification is well accepted.
Thank you.
Remo
________________________________________________________
| Dr. Remo Badii | Paul Scherrer Institute |
| Nonlinear Dynamics and | 5232 Villigen PSI |
| Stochastic Processes Group | Switzerland |
|____________________________|___________________________|
| badii "at" psi.ch | http://www1.psi.ch/~badii |
|____________________________|___________________________|
Reply to: