Hi,
I was wondering if there was any tool available in freebsd for handling
information, specifically configuration files, package information and such.
I know all information is available via text files however in order to access
the information the program might have to hard code the retreva
On Saturday, 16 June 2007 at 14:22:50 +0200, David Naylor wrote:
> Hi,
>
> I was wondering if there was any tool available in freebsd for handling
> information, specifically configuration files, package information and such.
> I know all information is available via text files however in order
David Naylor wrote:
> So:
> 1) What tools are there for accessing information (i.e. libraries)?
> 2) If so is there any unification of the interface?
> 3) If no to any of the above, is there a need for such tools and should it be
> a unified interface (not just specific subsets)?
If everything g
So who, exactly, is the best person to write to requesting
docs for AMD/ATI graphics/video chips?
We need to politely inform them that
There are a lot of operating systems out there,
and they all need high quality, fully functional drivers.
FreeBSD, NetBSD, OpenBSD, Plan-9
On Sat, Jun 16, 2007 at 10:33:00AM +0100, Dieter wrote..
> So who, exactly, is the best person to write to requesting
> docs for AMD/ATI graphics/video chips?
>
> We need to politely inform them that
>
> There are a lot of operating systems out there,
> and they all need high quality,
Wilko Bulte wrote:
On Sat, Jun 16, 2007 at 10:33:00AM +0100, Dieter wrote..
So who, exactly, is the best person to write to requesting
docs for AMD/ATI graphics/video chips?
We need to politely inform them that
There are a lot of operating systems out there,
and they all nee
On Sat, Jun 16, 2007 at 02:16:48PM -0700, Garrett Cooper wrote..
> Wilko Bulte wrote:
> >On Sat, Jun 16, 2007 at 10:33:00AM +0100, Dieter wrote..
> >
> >>So who, exactly, is the best person to write to requesting
> >>docs for AMD/ATI graphics/video chips?
> >>
> >>We need to politely inform them
Tim Kientzle wrote:
As Joerg said, though, you're not likely to gain much from
this. pkg_install is almost entirely disk bound.
Going back to this particular comment, has anybody really looked
into the speed of mtree(3)? That was the next stop that I planned on
looking at after I make my ch
Also, were the bottlenecks seen in pkg_delete and pkg_add, or does it
appear to be distributed across the board?
The biggest time sink in pkg_add is writing each file to a temp
dir then copying it to its final location. There are a couple
of strategies for avoiding this (by writing the files
What does this program do?
#include
int main(void)
{
printf("%u\n", 0x2a);
return 0;
}
Docs are more important than drivers. Please ask for
docs.
MC
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hac
Tim Kientzle wrote:
Also, were the bottlenecks seen in pkg_delete and pkg_add, or does
it appear to be distributed across the board?
The biggest time sink in pkg_add is writing each file to a temp
dir then copying it to its final location. There are a couple
of strategies for avoiding this
11 matches
Mail list logo
