lkml.org 
[lkml]   [1999]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: initrd/ramdisk problems, differences 2.2.1 vs. 2.2.5

Hi Riley, hi Dave,

I've found the main error, and it was mine.

If /sbin/init is dependant on shared libraries (and also /bin/sh), and
those libraries and the loader reside on /lib, which is on /dev/ram2,
then by re-mounting the root device /dev/ram1 while not having /dev/ram2
no dynamically linked program could be started.
The ram disk itself was completely correct.

It's sometime so easy and hard to find such an error !

After I've shuffled the programs and libraries a bit, now booting works as
never having done something else. The ramdisk version now works.

What's persisting now is the difference between 2.2.1 and 2.2.5 with
d_count and re-mounting the initial ramdisk, but that's an error which I
will report seperately into linux-kernel. May be I will report the
solution, too.

Thanks for your help and your ideas. If I could help you, feel free to
ask, too.

Regards

Frank


Frank Bernard
frankb@ipf.de
http://www.linux-firewall.de


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.976 / U:2.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site