From: Rik van Riel <riel@conectiva.com.br>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problem with vgscan/ vgcfgrestore
Date: Tue, 13 Mar 2001 23:17:23 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0103132316220.2056-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <20010313232626.A31056@cistron.nl>
On Tue, 13 Mar 2001, Wichert Akkerman wrote:
> Previously Andreas Dilger wrote:
> > Wichert writes:
> > > I figured that out by now. I think I'll add the LVM10 ioctls to
> > > strace 4.4 actually :)
> >
> > That would be nice.
>
> Turns out this is impossible: LVM made the same mistake some of the
> OSS sound drivers did and used ioctl numbers that the kernel already
> uses for other purposes. This is not a problem for the kernel itself,
> but means a tool like strace can't decode syscalls.
Good thing this can be fixed with IOP-11 in 2.5 ;)
(at least, I can't really see a large base of user
programs becoming dependant on the LVM ABI...)
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com.br/
next prev parent reply other threads:[~2001-03-14 2:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 18:40 [linux-lvm] Problem with vgscan/ vgcfgrestore Daniel Whicker
2001-03-12 23:19 ` Andreas Dilger
2001-03-13 0:16 ` Daniel E Whicker
2001-03-13 0:23 ` Wichert Akkerman
2001-03-13 0:56 ` Andreas Dilger
2001-03-13 1:14 ` Wichert Akkerman
2001-03-13 1:40 ` Andreas Dilger
2001-03-13 22:26 ` Wichert Akkerman
2001-03-13 23:02 ` Andreas Dilger
2001-03-14 2:17 ` Rik van Riel [this message]
2001-03-13 5:12 ` AJ Lewis
2001-03-13 9:41 ` Jason Walker
2001-03-13 9:57 ` Patrick Caulfield
2001-03-13 17:35 ` AJ Lewis
2001-03-13 0:59 ` Andreas Dilger
2001-03-13 7:41 ` Luca Berra
2001-03-13 17:40 ` AJ Lewis
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=Pine.LNX.4.21.0103132316220.2056-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--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).