public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Sidney Amani <amani_s@epitech.net>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] mtd-utils export libraries
Date: Wed, 07 Jan 2009 18:15:44 +0200	[thread overview]
Message-ID: <1231344944.6608.87.camel@localhost.localdomain> (raw)
In-Reply-To: <8bd0f97a0901070808n48bfd6a4vd7693ff085d6bf72@mail.gmail.com>

On Wed, 2009-01-07 at 11:08 -0500, Mike Frysinger wrote:
> On Wed, Jan 7, 2009 at 07:39, Sidney Amani wrote:
> > What we are trying to do is an UBI based userspace filesystem (using fuse).
> > We use the libubi to get volumes and devices info (ubi_get_dev_info,
> > ubi_get_vol_info, ubi_get_dev_info1, ubi_get_vol_info1).
> > Otherwise we communicate with the UBI volume through the cdev driver.
> > I am not sure a shared library is really desirable, probably not,
> > anyway it's not fundamental for us...
> > I particularly though that it could be useful for ubi-tools but I also
> > realize that it's much more restrictive to have shared libraries.
> 
> i'm not terribly familiar with the fuse implementation details.  are
> new filesystems plugins or shared libraries or standalone executables
> or ... ?  i.e. are you going to be linking the UBI code into another
> library or into a final application ?

I believe they should first actually _develop_ their file-system. I
believe they will change/improve the libubi a lot during the
development. And then we may think about a shared library.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-01-07 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 14:15 [PATCH 0/2] mtd-utils export libraries Sidney Amani
2008-12-18 14:37 ` Artem Bityutskiy
2008-12-18 20:24   ` Mike Frysinger
2009-01-06 15:16     ` Mike Frysinger
2009-01-07 12:39       ` Sidney Amani
2009-01-07 16:08         ` Mike Frysinger
2009-01-07 16:15           ` Artem Bityutskiy [this message]
2009-01-07 16:20             ` Mike Frysinger

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=1231344944.6608.87.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=amani_s@epitech.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vapier.adi@gmail.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