[oi-dev] Next #oi-meeting 28.2.2012 7PM GMT

2012-02-28 Thread Bayard G. Bell
Apologies for the late notice. I expect tonight will be mostly
housekeeping: status on deliverables discussed at recent meetings.

Cheers,
Bayard


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] [userland] Re: 1262 Berkeley-db package

2012-02-28 Thread Igor Kozhukhov
I have berkeleydb-5.1 at dilos-userland(from oracle-userland with additional
build flags for DEB tools) - works well with DEB tools such as: reprepro,
apt

You can try to check it on my IPS shared repo at
http://apt.dilos.org:1/:
database/berkeleydb-5@5.1.25,5.11-1.1.1:20120219T012952Z


Best regards,
-Igor

From:  Bayard Bell 
Reply-To:  
Date:  Tue, 28 Feb 2012 13:59:47 +
To:  OpenIndiana Developer mailing list ,

Subject:  [userland] Re: [oi-dev] 1262 Berkeley-db package

> Was this ever committed? I reckon we need libdb (I need it for something ATM),
> and I don't find it in the history. I'm happy to pick this up and run with it.
> 
> Cheers,
> Bayard
> 
> On Wed, Oct 5, 2011 at 10:05 AM, Guido Berhoerster 
> wrote:
>> * Alasdair Lumsden  [2011-10-05 01:31]:
>>> >
>>> > On 3 Oct 2011, at 23:31, Bayard G. Bell wrote:
>>> >
 > > On Mon, 2011-10-03 at 17:08 -0400, Alex Viskovatoff wrote:
> > >> On Mon, 2011-10-03 at 16:34 -0400, Josef 'Jeff' Sipek wrote:
>> > >>> Bayard made a good point, one will generally want multiple versions
of
>> > >>> bdb.
>> > >>> Thoughts about having bdb-4.8 (and bdb-5.2)?
> > >>
> > >> Can you or he give examples of why one would want that? It would be a
> > >> nuisance, because one would have to decide on some naming convention,
so
> > >> that multiple versions could be installed together. Do Linux
> > >> distributions ship multiple versions of bdb?
 > >
 > > Ubuntu, for example, delivers libdb4.6, libdb4.7, and libdb4.8 for
 > > libraries. (I'm running BackTrack 5, which is based off 10.04, so this
 > > is a bit dated.) The distro simply doesn't deliver any links to the
 > > libraries, so everything has to decide which version to link against by
 > > both major and minor version. I've ended up with one each for the core
C
 > > runtime because I have essentially three packages, each using a
 > > different version. I've seen similar things in other porting
 > > environments, which leads me to suspect that, if there's a nuisance
 > > argument, it's that, as a porting system carries more packages, it
 > > decides the greatest nuisance is forcing them all to use one version of
 > > BDB.
>>> >
>>> > That's an important point.
>>> >
>>> > That presumably means drop:
>>> >
>>> > link path=usr/lib/libdb-4.so target=libdb-4.8.so 
>>> > link path=usr/lib/libdb.so target=libdb-4.8.so 
>> 
>> You should have those links at least for the "default version" so
>> the linker finds it when passed -ldb.
>> --
>> Guido Berhoerster
>> 
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
> 
>  illumos-userland | Archives
> 
>   |
> Modify 
>  f>  Your Subscription 


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] 1262 Berkeley-db package

2012-02-28 Thread Bayard Bell
Was this ever committed? I reckon we need libdb (I need it for something
ATM), and I don't find it in the history. I'm happy to pick this up and run
with it.

Cheers,
Bayard

On Wed, Oct 5, 2011 at 10:05 AM, Guido Berhoerster wrote:

> * Alasdair Lumsden  [2011-10-05 01:31]:
> >
> > On 3 Oct 2011, at 23:31, Bayard G. Bell wrote:
> >
> > > On Mon, 2011-10-03 at 17:08 -0400, Alex Viskovatoff wrote:
> > >> On Mon, 2011-10-03 at 16:34 -0400, Josef 'Jeff' Sipek wrote:
> > >>> Bayard made a good point, one will generally want multiple versions
> of
> > >>> bdb.
> > >>> Thoughts about having bdb-4.8 (and bdb-5.2)?
> > >>
> > >> Can you or he give examples of why one would want that? It would be a
> > >> nuisance, because one would have to decide on some naming convention,
> so
> > >> that multiple versions could be installed together. Do Linux
> > >> distributions ship multiple versions of bdb?
> > >
> > > Ubuntu, for example, delivers libdb4.6, libdb4.7, and libdb4.8 for
> > > libraries. (I'm running BackTrack 5, which is based off 10.04, so this
> > > is a bit dated.) The distro simply doesn't deliver any links to the
> > > libraries, so everything has to decide which version to link against by
> > > both major and minor version. I've ended up with one each for the core
> C
> > > runtime because I have essentially three packages, each using a
> > > different version. I've seen similar things in other porting
> > > environments, which leads me to suspect that, if there's a nuisance
> > > argument, it's that, as a porting system carries more packages, it
> > > decides the greatest nuisance is forcing them all to use one version of
> > > BDB.
> >
> > That's an important point.
> >
> > That presumably means drop:
> >
> > link path=usr/lib/libdb-4.so target=libdb-4.8.so
> > link path=usr/lib/libdb.so target=libdb-4.8.so
>
> You should have those links at least for the "default version" so
> the linker finds it when passed -ldb.
> --
> Guido Berhoerster
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] ntfs-3g and fuse

2012-02-28 Thread Jean-Pierre André

Hi Gordon,

I am posting them to you in a private mail, this
is a 31K file.

Regards

Jean-Pierre



Gordon Ross wrote:

Hi Jean-Pierre,

Thanks for your work on the OpenSolaris fuse implementation.

I integrated your previous patches into a repository based on my
previously published "skeleton" workspace, so that it can be more
easily built as it would be if integrated into illumos.  That's here:
   https://bitbucket.org/gwr/illumos-fuse1

As I recall, when I did that I had to go hunting for your patches.
Could you please provide me with pointers to unified diffs
relative to either the latest OpenSolaris fuse or your version
1.0AC.3?  If you can, I'll integrate (and probably clean up the
lint/cstyle issues again:)

Thanks,
Gordon

2012/2/28 Jean-Pierre André:
   

Hi,

I am now releasing the fuse kernel module for OpenIndiana. Ntfs-3g
now fully passes the standard tests with this kernel module and without
need of the workarounds I had to insert earlier to cope with the bad
behavior of the fuse kernel module originated from OpenSolaris.

A few optimizations would still be useful. I might have a look at them
if there is enough demand.

Available on http://b.andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
are three packages ready for use :

- a full ntfs-3g package in 32-bit mode with the fuse-lite library
  and ntfsprogs
- a full ntfs-3g package in 64-bit mode with the fuse-lite library
  and ntfsprogs
- a fuse kernel module package for both the 32-bit and 64-bit modes

The raw source files (not packaged according to OpenIndiana
standards) are also available there.

I am keeping these files available on line for some time. I also keep
the change sets available to whoever enters the source code of the
fuse kernel module into a public source code management
repository.

Enjoy,

Jean-Pierre



Jean-Pierre André wrote:
 

Hi,

Milan Jurik wrote:
   

Hi Jean-Pierre,

Jean-Pierre ANDRE píše v út 24. 01. 2012 v 15:16 +0100:
 

Hi,

As a maintainer of ntfs-3g, I have received bug reports on OpenIndiana.
Digging into them, I found there were almost all caused by the buggy fuse
kernel module, which nobody seems to care about. So I had to do it
myself
   



 
   


--
JP André
email jean-pierre.an...@wanadoo.fr



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] ntfs-3g and fuse

2012-02-28 Thread Jean-Pierre André

Hi Alasdair,

Alasdair Lumsden wrote:

Hi Jean-Pierre,

Would you have any interest in adding this to the illumos-userland build 
framework so that it ships with the distribution in future releases?
   


Well, the fuse kernel module is not userland, it is
a pluggable part of the kernel. Compiling it requires
the kernel headers instead of the usual libc

Anyway, packaging is different from developing and
debugging. For the file system proper (which is "userland")
ntfs-3g provides a "tarball", with a standard building
procedure (configure, make, install) which the distributions
pack according to their own rules and tools.

For a kernel module, dedicated to a specific OS this is
meaningless. Is there a universal format which should
be used for interfacing the developers and the packagers
so that the developers can remain independent of the
distributors (and remain independent of the proprietary
tools from Oracle) ?

Regards

Jean-Pierre


On 28 Feb 2012, at 09:58, Jean-Pierre André wrote:

   

Hi,

I am now releasing the fuse kernel module for OpenIndiana. Ntfs-3g
now fully passes the standard tests with this kernel module and without
need of the workarounds I had to insert earlier to cope with the bad
behavior of the fuse kernel module originated from OpenSolaris.

A few optimizations would still be useful. I might have a look at them
if there is enough demand.

Available on http://b.andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
are three packages ready for use :

- a full ntfs-3g package in 32-bit mode with the fuse-lite library
  and ntfsprogs
- a full ntfs-3g package in 64-bit mode with the fuse-lite library
  and ntfsprogs
- a fuse kernel module package for both the 32-bit and 64-bit modes

The raw source files (not packaged according to OpenIndiana
standards) are also available there.

I am keeping these files available on line for some time. I also keep
the change sets available to whoever enters the source code of the
fuse kernel module into a public source code management
repository.

Enjoy,

Jean-Pierre


Jean-Pierre André wrote:
 

Hi,

Milan Jurik wrote:
   

Hi Jean-Pierre,

Jean-Pierre ANDRE píše v út 24. 01. 2012 v 15:16 +0100:
 

Hi,

As a maintainer of ntfs-3g, I have received bug reports on OpenIndiana. Digging 
into them, I found there were almost all caused by the buggy fuse kernel 
module, which nobody seems to care about. So I had to do it myself
   



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
 


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

   


--
JP André
email jean-pierre.an...@wanadoo.fr



___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] ntfs-3g and fuse

2012-02-28 Thread Gordon Ross
Hi Jean-Pierre,

Thanks for your work on the OpenSolaris fuse implementation.

I integrated your previous patches into a repository based on my
previously published "skeleton" workspace, so that it can be more
easily built as it would be if integrated into illumos.  That's here:
  https://bitbucket.org/gwr/illumos-fuse1

As I recall, when I did that I had to go hunting for your patches.
Could you please provide me with pointers to unified diffs
relative to either the latest OpenSolaris fuse or your version
1.0AC.3?  If you can, I'll integrate (and probably clean up the
lint/cstyle issues again:)

Thanks,
Gordon

2012/2/28 Jean-Pierre André :
> Hi,
>
> I am now releasing the fuse kernel module for OpenIndiana. Ntfs-3g
> now fully passes the standard tests with this kernel module and without
> need of the workarounds I had to insert earlier to cope with the bad
> behavior of the fuse kernel module originated from OpenSolaris.
>
> A few optimizations would still be useful. I might have a look at them
> if there is enough demand.
>
> Available on http://b.andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
> are three packages ready for use :
>
> - a full ntfs-3g package in 32-bit mode with the fuse-lite library
>  and ntfsprogs
> - a full ntfs-3g package in 64-bit mode with the fuse-lite library
>  and ntfsprogs
> - a fuse kernel module package for both the 32-bit and 64-bit modes
>
> The raw source files (not packaged according to OpenIndiana
> standards) are also available there.
>
> I am keeping these files available on line for some time. I also keep
> the change sets available to whoever enters the source code of the
> fuse kernel module into a public source code management
> repository.
>
> Enjoy,
>
> Jean-Pierre
>
>
>
> Jean-Pierre André wrote:
>>
>> Hi,
>>
>> Milan Jurik wrote:
>>>
>>> Hi Jean-Pierre,
>>>
>>> Jean-Pierre ANDRE píše v út 24. 01. 2012 v 15:16 +0100:

 Hi,

 As a maintainer of ntfs-3g, I have received bug reports on OpenIndiana.
 Digging into them, I found there were almost all caused by the buggy fuse
 kernel module, which nobody seems to care about. So I had to do it
 myself
>
>
>

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] ntfs-3g and fuse

2012-02-28 Thread Alasdair Lumsden
Hi Jean-Pierre,

Would you have any interest in adding this to the illumos-userland build 
framework so that it ships with the distribution in future releases?

Regards,

Alasdair


On 28 Feb 2012, at 09:58, Jean-Pierre André wrote:

> Hi,
> 
> I am now releasing the fuse kernel module for OpenIndiana. Ntfs-3g
> now fully passes the standard tests with this kernel module and without
> need of the workarounds I had to insert earlier to cope with the bad
> behavior of the fuse kernel module originated from OpenSolaris.
> 
> A few optimizations would still be useful. I might have a look at them
> if there is enough demand.
> 
> Available on http://b.andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
> are three packages ready for use :
> 
> - a full ntfs-3g package in 32-bit mode with the fuse-lite library
>  and ntfsprogs
> - a full ntfs-3g package in 64-bit mode with the fuse-lite library
>  and ntfsprogs
> - a fuse kernel module package for both the 32-bit and 64-bit modes
> 
> The raw source files (not packaged according to OpenIndiana
> standards) are also available there.
> 
> I am keeping these files available on line for some time. I also keep
> the change sets available to whoever enters the source code of the
> fuse kernel module into a public source code management
> repository.
> 
> Enjoy,
> 
> Jean-Pierre
> 
> 
> Jean-Pierre André wrote:
>> Hi,
>> 
>> Milan Jurik wrote:
>>> Hi Jean-Pierre,
>>> 
>>> Jean-Pierre ANDRE píše v út 24. 01. 2012 v 15:16 +0100:
 Hi,
 
 As a maintainer of ntfs-3g, I have received bug reports on OpenIndiana. 
 Digging into them, I found there were almost all caused by the buggy fuse 
 kernel module, which nobody seems to care about. So I had to do it 
 myself
> 
> 
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] ntfs-3g and fuse

2012-02-28 Thread Jean-Pierre André

Hi,

I am now releasing the fuse kernel module for OpenIndiana. Ntfs-3g
now fully passes the standard tests with this kernel module and without
need of the workarounds I had to insert earlier to cope with the bad
behavior of the fuse kernel module originated from OpenSolaris.

A few optimizations would still be useful. I might have a look at them
if there is enough demand.

Available on http://b.andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
are three packages ready for use :

- a full ntfs-3g package in 32-bit mode with the fuse-lite library
  and ntfsprogs
- a full ntfs-3g package in 64-bit mode with the fuse-lite library
  and ntfsprogs
- a fuse kernel module package for both the 32-bit and 64-bit modes

The raw source files (not packaged according to OpenIndiana
standards) are also available there.

I am keeping these files available on line for some time. I also keep
the change sets available to whoever enters the source code of the
fuse kernel module into a public source code management
repository.

Enjoy,

Jean-Pierre


Jean-Pierre André wrote:

Hi,

Milan Jurik wrote:

Hi Jean-Pierre,

Jean-Pierre ANDRE píše v út 24. 01. 2012 v 15:16 +0100:

Hi,

As a maintainer of ntfs-3g, I have received bug reports on 
OpenIndiana. Digging into them, I found there were almost all caused 
by the buggy fuse kernel module, which nobody seems to care about. 
So I had to do it myself




___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev