Can't download any files yet can't delete any either.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
He/She very probably did not have to do that.
The default when creating filesystems is to create them with some room to spare (5%) - ony accessible/usable by the root user.
So: even if the filesystem appears to be full - it is only full for users - not for root.
Log in as root - delete the files to make room - voila...
Any distro, its a matter of putting /root on its own partition. On a prodn system you'll usually/often find /var is on its own partition for the same reason ie that's where most logging goes, so most likely to fill up first. Doesn't stop people logging on.
I have to slightly disagree - it seems weare talking about different things:
when a ext2/ext3 filesystem is created and there is no -m option given to mkfs.ext2/mkfs.ext3 then, by default, it will be created with 5% of the space only accessible to the root user - this has nothing to do with separate partitions.
Specify the percentage of the filesystem blocks reserved for the super-user. This avoids fragmentation, and allows root-owned daemons, such
as syslogd(8), to continue to function correctly after non-privileged processes are prevented from writing to the filesystem. The default
percentage is 5%.
I'm not sure (I don't know) how creating another filesystem like reiserfs ... handles this.
Separate important system partitions can also help preventing a user completely filling up a filesystem because he has no write permissions on them anyway.
In both cases - root can still fill anything up.