From: Adrian Phillips <a.phillips@dnmi.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel 2.2.19 support
Date: 04 Oct 2001 19:18:45 +0200 [thread overview]
Message-ID: <wvy9mrfhmy.fsf@freeze.oslo.dnmi.no> (raw)
In-Reply-To: <20011004111023.C31061@turbolinux.com>
>>>>> "Andreas" == Andreas Dilger <adilger@turbolabs.com> writes:
Andreas> What you need to do to "properly" fix this is add a lines
Andreas> like
Andreas> #if LINUX_VERSION_CODE > KERNEL_VERSION ( 2, 3, X) foo.de
Andreas> = bar; #endif
Andreas> around the two offending code sections, and find the
Andreas> appropriate kernel version where this entry was added.
Andreas> This can be done by looking at the kernel CVS:
Andreas> http://lxr.linux.no/
Yes, but what concerned me was if there was some equivalent for 2.2
(foo.dev22 = bar). I was going to check the LVM CVS to see what
changes had been done but was unable to login :-
bash-2.03$ cvs -d :pserver:cvs@cvs.globalfilesystem.org:/data/cvs login
Logging in to :pserver:cvs@cvs.globalfilesystem.org:2401/data/cvs
CVS password:
cvs login: authorization failed: server cvs.globalfilesystem.org rejected access to /data/cvs for user cvs
I did this according to the LVM CVS page,
Sincerely,
Adrian Phillips
--
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now? [OK]
next prev parent reply other threads:[~2001-10-04 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 11:00 [linux-lvm] kernel 2.2.19 support Jesus Manuel NAVARRO LOPEZ
2001-10-04 11:17 ` Adrian Phillips
2001-10-04 11:56 ` Jesus Manuel NAVARRO LOPEZ
2001-10-04 12:03 ` Adrian Phillips
2001-10-04 12:17 ` Jesus Manuel NAVARRO LOPEZ
2001-10-04 15:18 ` Adrian Phillips
2001-10-04 17:10 ` Andreas Dilger
2001-10-04 17:18 ` Adrian Phillips [this message]
2001-10-04 17:49 ` Andreas Dilger
2001-10-04 18:05 ` Adrian Phillips
2001-10-11 15:19 ` Patrick Caulfield
2001-10-04 17:23 ` Christoph Hellwig
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=wvy9mrfhmy.fsf@freeze.oslo.dnmi.no \
--to=a.phillips@dnmi.no \
--cc=linux-lvm@sistina.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).