Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
The standard form of the mount command, is
mount -t type device dir
Although it's possible to put options at the end of the command, you probably can't break apart the "device dir" sequence.
In other words, your command should be:
Code:
mount -t iso9660 -o loop /path/to/cdimage.raw /mnt/mount_point
or
Code:
mount /path/to/cdimage.raw /mnt/mount_point -t iso9660 -o loop
mount -t iso9660 -o loop /path/to/cdimage.raw /mnt/mount_point
# mount -t iso9600 -o loop /home/satimis/cdimage.raw /mnt/cdimage/
Code:
mount: could not find any device /dev/loop#
Quote:
or
Code:
mount /path/to/cdimage.raw /mnt/mount_point -t iso9660 -o loop
# mount /home/satimis/cdimage.raw /mnt/cdimage/ -t iso 9660 -o loop
Code:
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount
The mounting command posted on my first posting worked on other Linux distro but not on BLFS 6.1
I suspect it is the problem of loop device support. Reading "/usr/src/linux-2.6.11.12/.config" following were found
Code:
# CONFIG_BLK_DEV_LOOP is not set
CONFIG_CC_ALIGN_LOOPS=0
# modprobe loop
Code:
FATAL: Module loop not found.
Any folk on the forum has met this problem before? Shall I set "CONFIG_BLK_DEV_LOOP=y (or m)"?
didn't work because of the space between iso and 9660.Absolutely.
Sorry, that was my typing mistake.
Quote:
I should have caught that in the first place...
I made some search before postinng. I suspected whether I overlooked some other advices on google search. I have been using my command line posted on the first posing for prolonged time without problem. It is still working on chroot FC3, the host. Then I started to wonder whether the commands have been changed on the latest version of "cdrecord".
Obviously you don't have /dev/loop# , because linux clearly says so
You can however create them by hand. Use this command
mknod /dev/loop0 b 7 0
mknod /dev/loop1 b 7 1
In the same way you can create loop2 and up.
It is nice command to use on some rare occasions when the loopdevices don't exists,
but it probably won't be any good when you don't have loopdevices configured in your kernel.
Obviously you don't have /dev/loop# , because linux clearly says so
You can however create them by hand. Use this command
mknod /dev/loop0 b 7 0
mknod /dev/loop1 b 7 1
In the same way you can create loop2 and up.
Tks. That is what I was searching for apart from recompiling kernel. I'll test them on next occasion because the kernel already recompiled.
Why it needs more than one loop, "loop0", "loop1", "loop2", etc. Whether after running them "mount -t iso9660 -o loop /path/to/cdimage.raw /mnt/mount_point" will work.
> Why it needs more than one loop, "loop0", "loop1", "loop2", etc. Whether after running them
> "mount -t iso9660 -o loop /path/to/cdimage.raw /mnt/mount_point" will work.
It needs more than one loopdevices for mount severalfiles at once, but normally (with udev I guess) the loop devices will be started by mount. (Mostly with a limitation of 8 loopdevices)
Does Loop also give error when you boot?
It does so by me. After reading this I check my config of my debian kernel and my LFS kernel and see the following: LFS has loopdevices configured in the kernel and Debian has a module.
Maybe that causes my error.
Pity that I haven't yet tried my loopdevices under LFS(always work in a chroot)
I will check this case too one time, but thanks for pointing to this,
Hoes
First of all:
After installing modules you need to make sure you install modules for the loaded kernel:
If you use kernel 2.6.11-12-LFS-Local than you should make sure you are building and installing modules for this kernel.
Secondly:
There's a list of all modules which can be loaded. Maybe you forget to update this list.
Run the command: depmod to create this list for your current kernel.
Yes I did all. I spent a whole day to test them (sound and loop modules) without result. My discovery is "sound" module can't co-exist with "loop" modules. Either enable "sound" as module or "loop" as module, not both of them. Otherwise both died.
I hacked some information from Internet. I'll test them later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.