Would someone help with this please? I’ve looked all over in yast and I can’t find it. I need to install dmsdos. One of the requirements is
Kernel configuration
Additional Block devices
Loopback device support (CONFIG_BLK_DEV_LOOP) must be set to Y or M
Where may I find this setting? It is needed to mount a file as a file system.
Here is the download site.
On 01/12/2013 12:36 AM, LouBryan wrote:
> Loopback device support (CONFIG_BLK_DEV_LOOP) must be set to Y or M
> Where may I find this setting?
the instructions on this page
http://cmp.felk.cvut.cz/~pisa/dmsdos/faq.html reads “You need the
loopback block device driver (enable the loopback device during kernel
configuration)” which means you must compile the kernel, and when
setting up to do that, you must set that CONFIG_BLK_DEV_LOOP to Y or M
during the configuration…
i’ve never compiled a kernel (still a new guy), but there are others
here who have…maybe they can help more…
OR maybe all the openSUSE kernels already have that config set! (but i
would guess the default is ‘N’)
On Fri, 11 Jan 2013 23:36:02 +0000, LouBryan wrote:
> Would someone help with this please? I’ve looked all over in yast and I
> can’t find it. I need to install dmsdos. One of the requirements is
>
> Kernel configuration Additional Block devices Loopback device support
> (CONFIG_BLK_DEV_LOOP) must be set to Y or M
>
> Where may I find this setting? It is needed to mount a file as a file
> system.
> Here is the download site.
>
> http://cmp.felk.cvut.cz/~pisa/dmsdos/
$ zcat /proc/config.gz | grep LOOP
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_LOOPBACK_TARGET=m
CONFIG_RC_LOOPBACK=m
CONFIG_SND_ALOOP=m
That’s on my 12.2 system. /proc/config.gz shows the configuration of the
running kernel and what options were selected at compile time.
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
The installation process for openSUSE needs the loopback device. You may safely
assume that every openSUSE kernel includes that driver.
On 01/12/2013 01:39 AM, Larry Finger wrote:
> The installation process for openSUSE needs the loopback device. You may
> safely assume that every openSUSE kernel includes that driver.
thank you both…my guess of ‘n’ i see is wrong, and i had NO idea how
to not just guess…thx 
so, LouBryan as for your question: your ‘m’ is set and you are ready to
rock and roll…go for it!
On 2013-01-12 00:36, LouBryan wrote:
>
> Would someone help with this please? I’ve looked all over in yast and I
> can’t find it. I need to install dmsdos. One of the requirements is
dmsdos? what is that?
> Kernel configuration
> Additional Block devices
> Loopback device support (CONFIG_BLK_DEV_LOOP) must be set to Y or M
>
> Where may I find this setting?
In the kernel compilation settings.
Forget it, that setting is default.
Minas-Anor:~ # grep CONFIG_BLK_DEV_LOO /boot/config-3.1.10-1.16-desktop
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
Minas-Anor:~ #
> It is needed to mount a file as a file
> system.
man losetup.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
Thanks to everyone for your replies. I checked and mine is set to m. So I’m good to go. I’ll let you know if it works.
This software allows mounting an M$ compressed drive. I found a box of floppies in storage from about 20 years ago that are compressed. I can’t read them. I’d like to see what’s on them before I throw them away. The games back then had a kluge user interface, but they were still fun. I’d hate to just throw them away, at least without seeing what’s on them.
The floppies are compressed with dblspace.000. This is the original drive compression software that M$ got in hot water for. Something about selling somebody else’s compression software as their own. So, in the next version of M$ (6.2 I think) they started vending their own home grown version. It was supposed to be compatible with the earlier version. But I tried to look at one of the floppies on a M$ XP system, and it could not read it. I didn’t have time to look at how I might get it to work.
I found dmsdos looking in wikipedia for dblspace. It’s supposed to be compatible with about a half dozen versions of drive compression software. All I want is to mount it read only and copy the files off. Then, the floppies are good for plastic recycle.
This has to rebuild the whole kernel. It’s asking me to do this.
cd /usr/src/linux
make zlilo
make modules_install
Is there something else I need to do instead of zlilo. Didn’t that change to grub something or other?
On 2013-01-15 04:36, LouBryan wrote:
>
> This has to rebuild the whole kernel. It’s asking me to do this.
>
>
> Code:
> --------------------
>
> cd /usr/src/linux
> make zlilo
> make modules_install
>
> --------------------
>
>
> Is there something else I need to do instead of zlilo. Didn’t that
> change to grub something or other?
Why do you want to do that? The openSUSE kernel has loopback support
included since many years.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
I wasn’t sure if it needed to recompile the kernel, so I just followed the install instructions. The kernel compile died with undefined reference to _mmx_memcopy in arch/x86/boot/compressed/vmlinux. But, it did not write any /tmp/*.log files, as it said it was going to if it needed to make changes. So, I’m thinking that a recompile of kernel is not necessary for OpenSUSE.
Now, I’m just trying to compile the dmsdos sources and I get some errors that all look like this:
<snip>
Dmsdos is now configured. Do a 'make clean; make' to (re)compile.
make dep
make[1]: Entering directory `/tmp/dmsdos-0.9.2.2/src'
./check.sh
Checking kernel configuration...
kernel configuration is OK.
gcc -w -E -MM -D__KERNEL__ -D__MODULE__ -DMODULE dblspace*.c dstacker*.c > depend
In file included from dmsdos.h:38:0,
from dblspace_alloc.c:38:
/usr/include/linux/version.h:2:2: error: #error "======================================================="
/usr/include/linux/version.h:3:2: error: #error "You should not include /usr/include/{linux,asm}/ header"
/usr/include/linux/version.h:4:2: error: #error "files directly for the compilation of kernel modules."
/usr/include/linux/version.h:5:2: error: #error ""
/usr/include/linux/version.h:6:2: error: #error "glibc now uses kernel header files from a well-defined"
/usr/include/linux/version.h:7:2: error: #error "working kernel version (as recommended by Linus Torvalds)"
/usr/include/linux/version.h:8:2: error: #error "These files are glibc internal and may not match the"
/usr/include/linux/version.h:9:2: error: #error "currently running kernel. They should only be"
/usr/include/linux/version.h:10:2: error: #error "included via other system header files - user space"
/usr/include/linux/version.h:11:2: error: #error "programs should not directly include <linux/*.h> or"
/usr/include/linux/version.h:12:2: error: #error "<asm/*.h> as well."
/usr/include/linux/version.h:13:2: error: #error ""
/usr/include/linux/version.h:14:2: error: #error "Since Linux 2.6, the kernel module build process has been"
/usr/include/linux/version.h:15:2: error: #error "updated such that users building modules should not typically"
/usr/include/linux/version.h:16:2: error: #error "need to specify additional include directories at all."
/usr/include/linux/version.h:17:2: error: #error ""
/usr/include/linux/version.h:18:2: error: #error "To build kernel modules, ensure you have the build environment "
/usr/include/linux/version.h:19:2: error: #error "available either via the kernel-devel and kernel-<flavor>-devel "
/usr/include/linux/version.h:20:2: error: #error "packages or a properly configured kernel source tree."
/usr/include/linux/version.h:21:2: error: #error ""
/usr/include/linux/version.h:22:2: error: #error "Then, modules can be built using:"
/usr/include/linux/version.h:23:2: error: #error "make -C <path> M=/home/abuild/rpmbuild/BUILD/linux-glibc-devel-3.4"
/usr/include/linux/version.h:24:2: error: #error ""
/usr/include/linux/version.h:25:2: error: #error "For the currently running kernel there will be a symbolic "
/usr/include/linux/version.h:26:2: error: #error "link pointing to the build environment located at "
/usr/include/linux/version.h:27:2: error: #error "/lib/modules/2.6.37.6-0.11-xen/build for use as <path>."
/usr/include/linux/version.h:28:2: error: #error ""
/usr/include/linux/version.h:29:2: error: #error "If you are seeing this message, your environment is "
/usr/include/linux/version.h:30:2: error: #error "not configured properly. "
/usr/include/linux/version.h:31:2: error: #error ""
/usr/include/linux/version.h:32:2: error: #error "Please adjust the Makefile accordingly."
/usr/include/linux/version.h:33:2: error: #error "======================================================="
In file included from dblspace_alloc.c:38:0:
dmsdos.h:622:5: error: #error Unknown readpage parameters
In file included from dmsdos.h:38:0,
from dblspace_buffer.c:42:
/usr/include/linux/version.h:2:2: error: #error "======================================================="
/usr/include/linux/version.h:3:2: error: #error "You should not include /usr/include/{linux,asm}/ header"
<snip>
I don’t know how to use ‘make’ all that well. Could somebody give me a tip on how to adjust the makefile?
On 2013-01-15 13:26, LouBryan wrote:
> I don’t know how to use ‘make’ all that well. Could somebody give me a
> tip on how to adjust the makefile?
No, the developers of that program have to be told to adapt their
software to the current kernel. Their job, that is.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Sent an email to the two developers. One bounced. From the other, he replied that it’s been a long time since it’s been maintained. Doesn’t have any updates above version 2 linux kernel. I’m pretty much on my own to do the updates. I can’t follow this code, so I’m giving up on that.
Tried DosBox, it does not work. Pretends to work, but fails to recognize what is a local drive or not. Tried VBoxGtk, showed promise, but I couldn’t figure out how to install Win9x os.
I finally got an old Win95 machine from a friend and used that successfully to uncompress the floppies.
Lesson learned (again), NEVER store backups in proprietary formats like M$. ALWAYS use an open format like posix tar.