Austin Gonyou wrote:
> Yeah..I finally just figured well, I've seen posts saying that the
> linux-2.4-xfs was the devel, and the devel was upped to 2.4.4, so, that
> makes sense... I've gonethrough configuring, and I'll build soon.
this seem like a lot of work just to disable devfs
where as
% vi lilo.conf
append="devfs=nomount"
% lilo -v
% reboot
is quite simple.
>
>
> --
> Austin Gonyou
> Systems Architect, CCNA
> Coremetrics, Inc.
> Phone: 512-796-9023
> email: austin@xxxxxxxxxxxxxxx
>
> On Thu, 3 May 2001, Seth Mos wrote:
>
> > On Thu, 3 May 2001, Austin Gonyou wrote:
> >
> > > I should've been more specific. I was under the assumption that you
> > > couldn't really use devfsd if devfs was not compiled into the kernel.
> > > Sorry for the confusion. What I really want to do is patch a 2.4.4 kernel
> > > to use XFS without using devfs. That part I don't think would be an issue,
> > > and I understand all that's involved here. One thing I'd like to be able
> > > to do though is to know how to properly patch a 2.4.4 kernel upto xfs.
> > > Should I get a 2.4.2 kernel, patch it with xfs, then patch it up to 2.4.4?
> > > Ideas?
> >
> > Just check out the linux-2.4-xfs tree from CVS. This one is currently
> > based on 2.4.4. See the Getting XFS from CVS page. Patching 2.4.2 with
> > XFS would be no problem, but patching this from 2.4.2 to 2.4.4 would be a
> > serious issue. XFS and other journaling fs are dependent on VM behaviour
> > and are thus very closely intergrated.
> >
> > If you know how to build kernels this shoudl not be a problem after
> > getting the tree fom CVS. If not, it's not that difficult.
> > Linuxdoc.org has al the neccesary kernel building howto's if neccesary.
> >
> > Good luck
> > Seth
> >
--
Russell Cattelan
--
Digital Elves inc. -- Currently on loan to SGI
Linux XFS core developer.
|