SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So I proceeded to "modprobe loop" and it said that it doesn't exist. I read that I have to make sure loopback filesystem support is compiled into my kernel but I couldn't find an option for it in the config. Where would this be or what am I doing wrong? Thanks a lot.
from man mount...
mount -t type device dir
This tells the kernel to attach the file system found on device (which is of type type) at the directory dir.
The previous contents (if any) and owner and mode of dir become invisible, and as long as this file system remains mounted, the pathname dir refers to the root of the file system on device.
...but you can't use what's mounted there.
but anyway good to know....
Yes, I was root user when I tried that :-\ I have also tried creating a new mountpoint, in my kernel configuration it says that it's built-in, and I have "7 loop" listed under Block Devices when I run "cat /proc/devices".
Last edited by darkarcon2015; 02-02-2005 at 02:45 PM.
Originally posted by darkarcon2015 Yes, same error.
EDIT *** SOLVED *** I had to copy the *.iso from my windows partition into my linux partition.
Sorry to reanimate this old thread's corpse, but I had the very same problem as darkacron2015, and the same solution worked for me as well. Basically all I wanted to do was watch a dvd iso located on my NTFS partition, but I ended up having to copy all four and a half gig of it to my home directory to do so.
I am curious: I've mounted numerous isos of various descriptions from my Windows partitions before, and now I can't seem to suddenly. Can somebody tell me what the explanation might be?
I have loopback support built directly in to my kerenel, I even copied the iso to my local filesystem (though you shouldn't need to do this, it'll mount over nfs or smb just fine).. and yet I still couldn't get it to mount.. I specified the file system type, you normally don't really need to do this either.. It turned out it was simply a bad iso.. So, make sure you get the same results with other isos or try mounting them on other machines, just to save yourself some time. I rebuilt my kernel and wasted about 40mins on this one. Don't make the same mistake.. Though, if you're here, you probably have a 'real' problem.