> Whoops, I obviously created a communications problem. I have no problem
> mounting the old HD in the new system. It's the new HD that I can't mount
> in the old system. The old system's fdisk indicates that the new partition
> is ext2 but I can't mount it that way. And the new system's fdisk also
> indicates ext2. I don't know what's wrong there, but it's more important to
> mount the old disk in the new system than the opposite anyway so that's not
> a major problem.
This is documented. See man mke2fs :
-O feature[,...]
Create the filesystem with the listed set of fea
tures (filesystem options). The following features
are supported: sparse_super, which cause the
filesystem to use sparse superblocks, and filetype,
which will cause the filesystem to store file type
information in directory entries. Currently, both
features are turned on by default unless mke2fs is
run on a system with a pre-2.2 Linux kernel. Warn
ing: Pre-2.2 Linux kernels do not properly support
the filesystems that use either of these two fea
tures. Filesystems that may need to mounted on
pre-2.2 kernels should be created with -O none
which will disable both of these features, even if
mke2fs is run on a system which can support these
features.
So if you install the new system, it is running unser 2.2 kernel and uses
these extension. Just format that partition under the old system and them
install the new without formatting.
> Each system, in it's own /boot, has a System.map and module-info. But
> from the behavior I've seen there has to be something else somewhere. I'm
> going to have to read the lilo and boot documentation very carefully to see
> what's going on.
>
> > > image=/boot/RTzImage
> > > label=rtlinux
> > > initrd=/boot/initrd-2.2.14-5.0.img
> > > read-only
> > > root=/dev/hdc1
> > > image=/boot/vmlinuz-2.0.36-0.7
These stupid initrd's are compressed images if initial ram disk - they
contain just modules (mainly disk drivers) which need to be loaded before the
disk may be accessed. I usually just get rid of them by compiling support for
my HD controller directly in the kernel, not as a module.
To look what is inside you may:
cp initrd-2.2.14-5.0.img tmp.img.gz
gzip -d tmp.img.gz
mount -o loop tmp.img /some/directory
Best regards,
--
Tomek
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
