LinuxQuestions.org - Creating a mini-linux home-made distribution

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Creating a mini-linux home-made distribution (https://www.linuxquestions.org/questions/linux-general-1/creating-a-mini-linux-home-made-distribution-25154/)

Ok, so that means if i put lilo on the disk along with the kernel, lilo will find the kernel during boot then boot up linux right?

Can i get a copy of Davix?

1. No, you need a lilo conf file

2. Ask someone else

Hi all,

I went to http://www.wam.umd.edu/~kefferb/floppy.html followed all the steps and made a disk. WHen i tried to boot, there's a kernel panic:

kernel panic: no init found. Try passing init= option to kernel.

Do any of you know what went wrong?

Thanks!

Did you create the init symbolic link according to instructions below:

Quote:

Now create some links to necessary system programs.
cd /mnt/floppy/sbin
ln -s ../bin/busybox init
ln -s ../bin/busybox modprobe # if you are using kernel modules
cd ../bin
ln -s busybox sh
ln -s busybox mount

If the init link is missing, you'll get that error. You'll also get the error if the link is in the wrong directory. It's supposed to be in the /sbin directory. You might have put it in the /bin directory.

One more thing, you need to fix your link to the site that has the instructions that you used. Remove the period ' . ' at the end of the link.

I'm sure i did the linkings correctly.

one thing i didn't mention. During the whole process i wasn't able to unmount the floppy. When i went "umount /mnt/floppy" it says device is busy. WHen i sent "umount /dev/fd0" it says it's not mounted.

I just looked through it real fast, but did you create the /dev/ files for the floppy disk

Davix is not ready, It hit the back burner for a while due to a lot of traveling around.

I didn't create files for /dev...
Oopps but that tutorial didn't say...

I'll try the whole process again. This time i'll follow the LInux Bootdisk howto. I had a read through the howto, it differs quite a lot from that site. It requires me to do a lot more things that site didn't even mention?

nutshell, I looked at the instructions again and I found that the floppy was never mounted. You probably got confused by the mounting of a loopback device.

A file was created named disk.ext2. It was then formatted as an ext2 file system. Then it was mounted as a loopback device at mount point /mnt/floppy. The mount point is what I believe confused you and why you got the error that the floppy was not mounted.

As for not being able to unmount /mnt/floppy, I believe they left out a step. They should have had you cd off of the loopback device before unmounting it. So, before you run umount /mnt/floppy, run cd ~. This should put you in your home directory and allow you to unmount the loopback device.

Sigh.............for some reason, after i deleted my old bzImage, i can't compile my kernel anymore! Here is the output of make dep zImage ( i also tried make dep bzImage). I've created my root filesystem and all that and all of a sudden i can't compile my kernel! Please give a hand. Here's the last few lines of output of make dep zImage:

Code:

make -C core

make[2]: Entering directory `/usr/src/linux-2.5.7/net/core'

make all_targets

make[3]: Entering directory `/usr/src/linux-2.5.7/net/core'

gcc -D__KERNEL__ -I/usr/src/linux-2.5.7/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686  -DKBUILD_BASENAME=sock  -c -o sock.o sock.c

sock.c: In function `sock_getsockopt':

sock.c:559: `TCP_LISTEN' undeclared (first use in this function)

sock.c:559: (Each undeclared identifier is reported only once

sock.c:559: for each function it appears in.)

sock.c: In function `sock_init_data':

sock.c:1192: `TCP_CLOSE' undeclared (first use in this function)

make[3]: *** [sock.o] Error 1

make[3]: Leaving directory `/usr/src/linux-2.5.7/net/core'

make[2]: *** [first_rule] Error 2

make[2]: Leaving directory `/usr/src/linux-2.5.7/net/core'

make[1]: *** [_subdir_core] Error 2

make[1]: Leaving directory `/usr/src/linux-2.5.7/net'

make: *** [_dir_net] Error 2

bash-2.05a# make dep zImage > /home/dyh/compileMsg.txt

md5sum: WARNING: 10 of 13 computed checksums did NOT match

sock.c: In function `sock_getsockopt':

sock.c:559: `TCP_LISTEN' undeclared (first use in this function)

sock.c:559: (Each undeclared identifier is reported only once

sock.c:559: for each function it appears in.)

sock.c: In function `sock_init_data':

sock.c:1192: `TCP_CLOSE' undeclared (first use in this function)

make[3]: *** [sock.o] Error 1

make[2]: *** [first_rule] Error 2

make[1]: *** [_subdir_core] Error 2

make: *** [_dir_net] Error 2

That's is pretty confusing. I don't see why they used mnt/floppy as a mount point for the file system on the hard drive.

Hi,

I'm now using the bootdisk howto now. So can you please answer my above question about not being able to compile the kernel?

Thanks a lot!

I also tried deleting the source, unpacking the source, and then tried compiling again and it still gave me the same error: which is the error 2 and 1s...ugh

Thanks

I can compile my kernel now. I just downloaded a different of kernel. One i have now is 2.4.18.

Ok i made another bootdisk with the linux bootdisk howto. WHen i tried to boot it it still gave me the error i had with the other disk i made with that other site:

kernel panic: no init found. Try passing init= option to kernel.

How about this. WOuld anyone be kind enough to provide me with a sample root filesystem file? (i don't mean a listing). For some reason the bootdisk howto requires much more than other tutorials. Or alternatively , would anyone be kind enough to let me send my rootfs to him/her to have a loook at it and spot anything i've done wrong?

Thanks

looks like several problems, It was pretty late so I did not check it all yet. But you need to go through it carefully.

here's the first thing I noticed

ls -l bin
total 205
-rwxr-xr-x 1 root root 208296 Jul 11 04:11 busybox*
lrwxrwxrwx 1 root root 7 Jul 11 04:12 mount -> busybox*
lrwxrwxrwx 1 root root 7 Jul 11 04:12 sh -> busybox*

link mount and sh to busybox?, no way that will work

and

where's /bin/login?

what's this?
ls -l sbin
total 0
lrwxrwxrwx 1 root root 16 Jul 11 04:11 init -> /mnt/bin/busybox

no such folder as /mnt/bin

got some needed /dev/files missing

console, kmem, mem, null

you need /etc/ld.so.conf and /etc/ld.so.cache

/etc/nsswitch.conf

passwd

your /lib folder only has one file. you need many more libs

you should have some /var folders like /var /var/log /var/run