Re: XFS

Bogdan Costescu <bogdan.costescu-hEciA7+sKtudPOQpRHQ53DeJuz7u0hKX@public.gmane.org>
Newsgroups gmane.linux.tao.general
Message-ID <Pine.LNX.4.44.0410251946050.5811-100000@kenzo.iwr.uni-heidelberg.de>
On Mon, 25 Oct 2004, Pasi Pirhonen wrote:

> I a not trying to hide anything. It's just that David said that he
> weill collect 'one unified set of SRPMS of U3 arches' to same some
> space for mirrors. U3 is not released, so there is no SRPMS still.

OK, my point was about having a unique kernel package (be it for
x86_64 only if you decide so) that more people can use and therefore
increase trust in its functionality. I am able to rebuild packages
myself and I've done some kernel hacking in the past, so I can produce
such a kernel package. But from this to actually putting it on a
production machine is a long way, especially with such a complex
change as XFS. However, if several people use the exact same package
_and_ share their experience, one can be confident enough at some
point to put this package on a production machine.

> There are some more SRPMS which are unique for releases i am
> maintaining (depending what David will merge in for ia32) and all
> the SRPMS will be available when the actuall release is made.

Maybe my initial message was not clear on this point, so I'll try to
make it now: I'm not asking for [insert favourite kernel module] to be
present in the official Tao kernel. I'm only asking if your extra
kernel (that you said you already made for your own purposes) could be
made available.

And a question for David: could this list be used also for discussions 
about these "non-official" kernels (or maybe other packages) ?

-- 
Bogdan Costescu

IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu-PDzUyZpvkMP/PDbm/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.