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.
Logged in as root, I'm unable to umount /dev/fd0. I get "umount: /mnt/floppy: device is busy". I realize that I need to be in some other directory than the mounted directory. I couldn't umount while sitting at /etc.
This has happened to me a couple of times before and I simply rebooted the machine... but it seems to me, that's the Windows approach to correcting a problem. I'm hoping to learn how to do this right. Is there a process that could be reloaded or restarted to get the floppy drive to respond again? I popped a disk out this morning without umounting it. Then, this afternoon, I edited the /etc/fstab file to add nosuid,nodev, to /dev/fd0 but, when I discovered I was having a problem with it, I commented out the line that I added with those params or args and uncommented the line I was using before I made the change. I don't know, for sure, if that means it should be back to the configuration it was prior to the change I made... but I do know it's not busy, even though it says it is.
your working directory is probably still in the floppy.
when u use the su command, you are working as 2 users, root, and normal user.
make sure you cd our of the /mnt/floppy as root, and as normal user, and issue the umount command as the same user who issued the mount command.
to be honest, you shouldnt really need to su at all to access the floppy.
Distribution: Slack Puppy Debian DSL--at the moment.
As far as I know, the easiest way to fix the problem of umounting a floppy after removing it is to put the original floppy back into the floppy drive and then umount it.
You don't mess with /etc/fstab or /etc/mtab. Bad things can happen.
What happens when you mount something is that there is an entry made in /proc/filesystems. (You really don't want to screw around with that either.) This means that the mounted filesystem exists in ram--which is why rebooting clears it. Yes, it can be done, but you probably really don't want to go there. (That is a hint.)
Doh! I have had a floppy or cd refuse to umount as root as well. I'm sure of it, because I've been too lazy to su and logged in as root. Maybe its just me.
Yeah... that's pretty funny. I was sure I was off the floppy... I was, logged in as root. But I didn't realize that I was still on the floppy as a user... or that it mattered. I exited out of root and sure enough, there I was sitting on the floppy. I got off and umounted, no problem.