On Tue, Nov 30, 2004 at 12:08:50AM +0200, Ira Abramov wrote:
Quoting Yedidyah Bar-David, from the post of Mon, 29 Nov:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More rpecisely :I'm not sure I have the .config file it was built with
).
Hello,
Thanks for your answer and the link; it was really a very
interesting lesson.
First , there is also a non-compressed image file on the 2.6.* kernel I
use. It resides, natuarally (?!) , in the compressed folder.
(/arch/i386/boot/compressed)
It is called vmlinux.
Running nm -a vmlinux | egrep
Hello,
Maybe it is more accurate to term the problem not so common
instead of theoretical.
Second, you suggested Look at /proc/filesystems. Do this right after boot
...
Well , this as you said, shows filesystems supported at the
moment, regardless of whether they are builtin or loaded as
On Tue, Nov 30, 2004 at 10:19:43AM +0200, Yedidyah Bar-David wrote:
Last note - I really do not understand this trend of compiling the
kernel with a modular ext3, while defaulting / to be ext3, therefore
forcing you to have an initrd, started by RH7.2. Of course some hardware
will require it
On Tue, Nov 30, 2004 at 10:36:47AM +0200, Dan Kaspi wrote:
Hello,
Maybe it is more accurate to term the problem not so common
instead of theoretical.
Second, you suggested Look at /proc/filesystems. Do this right after boot
Well , this as you said, shows filesystems supported at
Ira Abramov wrote:
Quoting Yedidyah Bar-David, from the post of Mon, 29 Nov:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More rpecisely :I'm not sure I have the .config file it was built with ).
2.6 added the option to include this file in the
On Tue, Nov 30, 2004 at 10:46:20AM +0200, Muli Ben-Yehuda wrote:
I think you're thinking about it the wrong way. RH kernels require you
to have an initrd if you want to use the default root=LABEL=XXX syntax
in lilo/grub, since the work of identifying the root partition is done
in in the
Quoting Yedidyah Bar-David, from the post of Tue, 30 Nov:
Last note - I really do not understand this trend of compiling the
kernel with a modular ext3, while defaulting / to be ext3, therefore
forcing you to have an initrd, started by RH7.2. Of course some
hardware will require it anyway,
On Tue, 30 Nov 2004, Dan Kaspi wrote:
Hello,
Thanks for your answer and the link; it was really a very
interesting lesson.
[.. snip ..]
So I ran dd like thus (I am not sure that I used the dd correctly as
I don't use it frequently):
First,I used skip=11 for 1 sector of boot sector and
On Mon, Nov 29, 2004 at 06:26:33PM +0200, Dan Kaspi wrote:
Hello,
This is a question which may be less practical and more theoretical,
I think it's very practical.
,but it interests me though:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More
Quoting Yedidyah Bar-David, from the post of Mon, 29 Nov:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More rpecisely :I'm not sure I have the .config file it was built with ).
2.6 added the option to include this file in the kernel itself, as
We can also look in the .config file. If we have m or y next to the
EXT3_FS= options
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ira Abramov
Sent: 30 2004 00:09
To: [EMAIL PROTECTED]
Subject: Re: ext3 in the kernel image or as a module
Quoting
On Mon, 29 Nov 2004, Dan Kaspi wrote:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More rpecisely :I'm not sure I have the .config file it was built with ).
I want to know if the ext3 was build into this kernel image or as a module.
question: on my old
On Tuesday 30 November 2004 00:08, Ira Abramov wrote:
Quoting Yedidyah Bar-David, from the post of Mon, 29 Nov:
I have a bzImage. It was built with 2.6.* kernel. I do not know the
configuarion
( More rpecisely :I'm not sure I have the .config file it was built
with ).
2.6
14 matches
Mail list logo
