On Wed, 2007-04-25 at 11:45 -0600, Tarun Reddy wrote: > On Apr 25, 2007, at 9:35 AM, Tarun Reddy wrote: > > > > > On Apr 25, 2007, at 4:33 AM, Johnny Hughes wrote: > > > >> On Tue, 2007-04-24 at 22:35 -0600, Tarun Reddy wrote: > >>> On Apr 24, 2007, at 4:05 PM, Johnny Hughes wrote: > >>> > >>>> On Tue, 2007-04-24 at 10:08 -0700, Akemi Yagi wrote: > >>>>>> I Just installed the new CentOSplus kernel package for CentOS 5 > >>>>>> on my > >>>>>> test workstation, so far so good. I was a bit surprised to note > >>>>>> that it > >>>>>> didn't include the IEEE1394/Firewire modules. Was this > >>>>>> intentional or > >>>>>> merely an oversight? I realize that including them in a > >>>>>> server is > >>>>>> probably a bad idea, but I had been using CentOS 4 with the -plus > >>>>>> kernel > >>>>>> on my workstation to grab video from my Sony DV camera. No > >>>>>> problem if > >>>>>> it's not going to be there, I can just build a custom kernel > >>>>>> if it's > >>>>>> that important to me. > >>>>> > >>>>> I submitted a request for the firewire support some time ago: > >>>>> > >>>>> http://bugs.centos.org/view.php?id=1909 > >>>>> > >>>>> So, hopefully it will be added... > >>>>> > >>>>> Akemi > >>>> > >>>> It was overlooked ... I will add this (and anything else that we > >>>> find we > >>>> need) and respin the kernels for final release. > >>> > >>> Sigh, > >>> This is what I get for being excited and update my machine before > >>> actually looking at the RPMs.... > >>> > >>> It appears that the jfs kernel module isn't built yet for the > >>> CentOSplus kernel. So while fsck.jfs does work, I can't get > >>> Centos to > >>> actually mount my jfs partition. Of course I may have screwed > >>> something up, too. > >>> > >>> I have this line in /etc/fstab > >>> /dev/md2 /export jfs > >>> defaults 1 1 > >>> > >>> and when I do a mount /export > >>> I get > >>> mount: unknown filesystem type 'jfs' > >>> > >>> uname -a > >>> Linux fw.tarun.homeip.net 2.6.18-8.1.1.el5.centos.plusxen #1 SMP Mon > >>> Apr 16 07:34:51 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux > >>> > >>> Any ideas? > >>> > >> > >> I have one .. somehow, the JFS was not turned on in the x86 > >> kernel ... > >> let me respin the kernels with all the proper config files and > >> turn on > >> firewire. > >> > >> I'll get another kernel out today for testing > >> > >> Thanks, > >> Johnny Hughes > >> > > That's funny, I actually look at that last night, but since I moved > > from i386 to x86_64, I only looked at the kernel-xen i386.config > > file in the kernel SRPM and saw that CONFIG_JFS_FS=m. Now that I > > look in the x86_64 kernel, it is not set. I'm going to try and > > rebuild as well.. just for the heck of it. > > > Well I changed that, and rebuilt the rpms, and no love. rpm -qpl > kernel or kernel-xen don't show any jfs components. kernel-debuginfo- > common shows a bunch of jfs stuff but they are just .c files. No help > there. > > I guess I'll see what Johnny comes up with. Probably a more serious > build bug. (FWIW, I just did a rpmbuild --bb kernel-2.6.spec after > install the SRPM) Here is the problem .... Red Hat has built some generic config file templates that they apply to the config files that are in the SOURCES directory (using a Perl script) before they copy them to the BUILD directory. These templates actually turn off things, even if you put them in the config files. I guess that this allows the same config files to be used for RHEL and FC ... with certain things that are on in FC turned off in RHEL. It took a little bit of time for me to actually see that RH had built this into the prep stage of the kernel SRPM. However, we should be set now ... holy cow ... now they are even building SRPMS that are smarter than me :D I will post another mail after I have moved the new kernels into place ... probably in less that 12 hours. Thanks, Johnny Hughes
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
