Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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 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
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
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.