When I booted, I had 3 error messages saying that I was'nt suppose to see and that I should look into the LFS book to correct this error. I did look, but sadly enough, I did'nt find what I was looking for.

The error was when loading :

/etc/rc.d/rcsysinit.d/S20mountproc

with an error code 32, if it means something to you

the same thing again for
/etc/rc.d/rcsysinit.d/S40mountfs

error code 96

and the last one

/etc/rc.d/rc3.d/S20network

error code 7


I hope you can help me
thanks
ccool

error codes don't mean much, we need the error message too. You'll find them above the "You shouldn't be reading this message..."

ok, I just rebooted to have the complete message.

The first one is:

Mounting proc file system
modprobe: modprobe: can't locate module default
mount: proc has wrong device number or fs type default not supported

the second one is:

Mounting remaining file system
warning: can't open /etc/mtab : No such file or device
modprobe: modprobe: can't locate module default
mount: proc has wrong device number or fs type default not supported

the last one is:

Setting default gateway
SIOCADDRT: Network is unreachable


That's pretty much it...

Those look like kernel problems to me. compile the kernel again but make sure that it has proc filesystem support, as well as support for your network card (that's where the SIOCADDRT is comming from.

I just re-compile my kernel... Everything is suppose to be in there, my network card is, I'm using the tulip driver, and the proc was there...

Maybe it's another thing ??? or there is something specific I need to put in the kernel compilation ??

I guess it's over my head then.... Is your driver and proc stuff enabled as modules?... if so, try compiling them in instead.

Are you copying your new kernel to boot along with System.map and running lilo again?

I already have linux mandrake installed on my pc. I just copied the lfskernel on /boot/ and I configured mandrake's lilo... Do I have to copy System.map too, and if so, how do I do it without removing mandrake System.map ???

I could be wrong, but I think that you copy System.map to the system that is going to use it, but you need to copy the kernel to /boot of both the system using it and the system with lilo.

try that out... compile your kernel in lfs, copy lfskernel and System.map to /boot. Then boot up mandrake, mount the lfs partition and copy $LFS/boot/lfskernel to /boot. Then run /sbin/lilo -v . I hope that helps....

Hi, I already did copy my lkskernel to my /boot in mandrake... I just did'nt copy the System.map, because I did'nt want to overwrite the mandrake's System.map...

when on mandrake...

/lfs/boot/System.map (from lfskernel compilation)
/lfs/boot/lfskernel (from compilation too..)
/boot/System.map (from original mandrake kernel)
/boot/lfskernel (a copy from the other one)
/boot/allotherstuff (originally there in mandrake 8.2)

this is how I put everything.

this is my lilo.conf in mandrake (I did run "lilo" after I made this configuration)

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
default=linux
keytable=/boot/qc-latin1.klt
lba32
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz
label=linux
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi quiet"
vga=788
read-only

image=/boot/lfskernel
label=LFS
root=/dev/hda7
read-only

I don't know buddy..... The only thing else that I can think of is maybe your /etc/fstab is wrong and that you need a different driver for your network card. If that is way off, you might have missed a crutial step when building the lfs??? what DOES your /etc/fstab look like?

exactly like this :

# Begin /etc/fstab
# filesystem mount-point fs-type options dump fsck-order

/dev/hda7 / reiserfs defaults 0 0
/dev/hda5 swap swap pri=1 0 0
proc /proc defaults 0 0
devpts /dev/pts devpts gid=4,mode=620 0 0


!!!

by the way, thanks for all your help

ah yes, I forgot... my network card seems to work... !?!?

Ccool

do you have "reiserfs" and "devpts" support in your kernel? I don't know if this would do anything to your proc mounting problem, but it might.

thanks, I found the problem... my fstab was not ok... now it is