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
).
PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: ext3 in the kernel image or as a module Date: Tue, 30 Nov 2004
02:09:52 +0200 (IST)
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
...
But my aim , as I said in my question , was to know exactly
whether ext3 is a builtin or loaded a modules.
Thnks,
Dan
From: Yedidyah Bar-David [EMAIL PROTECTED]
To: Dan Kaspi [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: ext3 in the kernel image or as a module
Date: Mon, 29 Nov 2004 21:12
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
was build into this kernel image or as a module.
(It seems to me that looking under /lib/modules/version/fs/ext3 does not
indicate it truly ; an ext3.ko could be put there afterwards)
While the practical solution can be configure it as a module or
as part of the image and the build it, it interests me if I
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
/proc/config.gz. You might look there.
I want to know if the ext3 was build into this kernel image or as a module.
(It seems to me that looking under /lib/modules
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
into all of their conf files,
and since the resault is a pretty long file, its pointless to send it to
the list. a based my assumption on the fact that i have an entry in
lilo.conf to the old kernel image as well, and its loading with no
problem, using the same configuration file.
May I suggest
that looks ok to you ?
debian adds a LOT of inline little howto's into all of their conf files,
and since the resault is a pretty long file, its pointless to send it to
the list. a based my assumption on the fact that i have an entry in
lilo.conf to the old kernel image as well, and its loading
On Mon, 2003-08-18 at 01:30, guy keren wrote:
On Sun, 17 Aug 2003, Amir Tal wrote:
debian sid, dell inspiron 4000 laptop.
installed kernel-image-2.6.0-test2-1 with apt-get. installation went
fine. took a look at lilo.conf after installing, looks ok to me.
when booting the new kernel i
On Sun, 17 Aug 2003, Amir Tal wrote:
debian sid, dell inspiron 4000 laptop.
installed kernel-image-2.6.0-test2-1 with apt-get. installation went
fine. took a look at lilo.conf after installing, looks ok to me.
when booting the new kernel i get a kernel panic, and a message that
tells meto
19 matches
Mail list logo
