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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
suddenly out of the blue i am facing this problme whilre making intrd images
i have done this a lot of time and now i am facing this problem
root@darkstar:/usr/src/linux-18.104.22.168# mkinitrd -k 2.6.11gm142 -o /boot/initrd-2.6.11gm142.img
cp: cannot create regular file `/tmp/tmp.1DbU0G/rootdev': No space left on device
cp: cannot create regular file `/tmp/tmp.1DbU0G/rootfs': No space left on device
i got he same error for compiling 2.4 kernel as well
it was going fine some time back
"no space left on device" is telling you your filesystem is full.
Do df -k /tmp/tmp.1DbU0G to see what it is mounted as and how full it is:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda9 472984 10739 437824 3% /tmp
If you see Use% at 100% then you need to clean up. It is possible that it is not at 100% when you start but is getting there during the process. If this is the case you can monitor it by opening a separate window and running:
df -k tmp.1DbU0G
This will repeat the output every 5 seconds. (Hit ctrl-C when done to break out of it.) If you see it hit 100% you need to clean up your filesystem.