From: Patrick Caulfield <patrick@tykepenguin.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Probleme while compiling last CVS kernel.
Date: Thu, 6 Jun 2002 19:43:27 +0100 [thread overview]
Message-ID: <20020606184327.GO1080@tykepenguin.com> (raw)
In-Reply-To: <1023388448.3cffab201378e@webmail.tiscalinet.be>
On Thu, Jun 06, 2002 at 08:34:08PM +0200, joel.soete@freebel.net wrote:
> Hi all,
>
> I do not have the opportunity to run a 64bits kernel but for 32bits kernel I run
> a patched kernel with last stable lvm-1.0.4 (and it is runing fine for at least
> two month).
> Humm which CONFIG_ parameter do I have to check to compile this src for 64-bits
> kernel.
> I can so try to see at least if it compiles well and report results.
I don't know about the 64bit compile switches (I only have a 32bit HP box) but
to get LVM running you'll need to take all the bits from
arch/sparc64/kernel/ioctl32.c inside the
#if defined(CONFIG_BLK_DEV_LVM) || defined(CONFIG_BLK_DEV_LVM_MODULE)
#endif
and replace the bits from arch/parisc/kernel/ioctl32.c with them. I suspect it
will work. If it does then get a patch together and put it into the CVS !
I'm pleased (though not very surprised) that LVM works OK on 32 bit machines.
patrick
aka caulfield@sistina.com
next prev parent reply other threads:[~2002-06-06 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 12:44 [parisc-linux] Probleme while compiling last CVS kernel Bruno Vidal
2002-06-06 13:00 ` Patrick Caulfield
2002-06-06 18:34 ` joel.soete
2002-06-06 18:43 ` Patrick Caulfield [this message]
2002-06-07 6:05 ` joel.soete
2002-06-07 7:16 ` joel.soete
2002-06-07 7:24 ` Patrick Caulfield
2002-06-07 7:28 ` joel.soete
2002-06-07 7:34 ` Patrick Caulfield
2002-06-07 7:39 ` joel.soete
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 15:31 joel.soete
2002-06-07 18:24 ` Patrick Caulfield
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=20020606184327.GO1080@tykepenguin.com \
--to=patrick@tykepenguin.com \
--cc=parisc-linux@lists.parisc-linux.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.