From: Kossey, Robert <bob.kossey@hp.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre version patchless kernel?
Date: Tue, 22 Jul 2008 23:22:15 -0400 [thread overview]
Message-ID: <4886A3E7.6050904@hp.com> (raw)
In-Reply-To: <4886A29C.2000009@hp.com>
We also see this on recent releases like 1.6.5.1. Why do you bother to
distribute kernel-lustre-smp RPMs if the kernels are not patched?
Thanks,
Bob
>> /
> />/ For the lustre version, the kernel portion indicates patchless...
> />/ Should it be something else?
> />/ />/ [root at operon22
> <http://lists.lustre.org/mailman/listinfo/lustre-devel> lustre]# more
> /proc/fs/lustre/version
> />/ > lustre: 1.9.50
> />/ > kernel: patchless
> />/ > build:
> 1.9.50-19691231190000-PRISTINE-.extra.linux-2.6.18-92.1.6-2.6.18-92.1.6-lustre-1.9.50
>
> /
> This is correct. For patched kernels there will be a version number
> here,
> indicating the VFS patch API version number. This hasn't changed in a
> long time because we are no longer changing the kernel VFS patches, and
> only a few older kernels still need them.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
>
>
next parent reply other threads:[~2008-07-23 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4886A29C.2000009@hp.com>
2008-07-23 3:22 ` Kossey, Robert [this message]
2008-07-28 13:03 ` [Lustre-devel] Lustre version patchless kernel? Brian J. Murrell
2008-07-28 16:07 ` Andreas Dilger
[not found] <488DD7C1.7010807@hp.com>
2008-07-28 14:38 ` Kossey, Robert
2008-07-30 9:35 ` Andreas Dilger
2008-07-30 15:52 ` Kossey, Robert
2008-07-30 21:19 ` Andreas Dilger
2008-07-21 15:01 [Lustre-devel] Cross posting of ADM information on opensolaris.org Rick Matthews
2008-07-21 20:29 ` Rick Matthews
2008-07-23 1:02 ` [Lustre-devel] Lustre version patchless kernel? Josephine Palencia
2008-07-23 1:20 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4886A3E7.6050904@hp.com \
--to=bob.kossey@hp.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.