On May 10, 2007, at 8:20 PM, Garrett Cooper wrote:
Yipes. The name of the game is to get something working in the base
system, instead of dragging in multiple 3rd party packages, with
licensing schemes that may not be aligned with the BSD license.
SQL's great, SQL's wonderful for db use,
On May 14, 2007, at 10:03 PM, Garrett Cooper wrote:
Bert JW Regeer wrote:
On May 12, 2007, at 5:14 AM, Philippe Laquet wrote:
Stanislav Sedov a écrit :
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree
On 2007-05-14 13:19, Alexander Leidinger [EMAIL PROTECTED] wrote:
Quoting Dag-Erling Smrgrav [EMAIL PROTECTED] (from Mon, 14 May 2007
11:31:25 +0200):
Note that we are apparently not the only ones dissatisfied with this
state of affairs. The following code is commonly found in rpm specs
Mike Meyer [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
Mike Meyer [EMAIL PROTECTED] writes:
How would setting LOCALBASE=/usr break this? Of course, equally valid
is the question what will break if I set LOCALBASE=/usr? Hmm. I
think I may found out
For
Alexander Leidinger [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
The existence of .la files is a bug.
I fully agree [but this needs to be addressed upstream]
Note that we are apparently not the only ones dissatisfied with this
state of affairs. The following code
Quoting Dag-Erling Smørgrav [EMAIL PROTECTED] (from Mon, 14 May 2007
11:31:25 +0200):
Alexander Leidinger [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
The existence of .la files is a bug.
I fully agree [but this needs to be addressed upstream]
Note that we are
Alexander Leidinger [EMAIL PROTECTED] writes:
Isn't this a property which can be set at build time? I mean: isn't
there a $OSNAME case where this can be set for a specific OS? So it
boil down to just set those two variables accordingly in the FreeBSD
case and to send a patch to the libtool
Alexander Leidinger [EMAIL PROTECTED] writes:
If this works well, you just have to submit this patch to the libtool
maintainers and wait until all (relevant) software packages are
updated to use the libtool version which comes with this change.
hahahahahahahaha
*sniff*
excuse me...
No
Quoting Dag-Erling Smørgrav [EMAIL PROTECTED] (from Mon, 14 May 2007
13:44:37 +0200):
Alexander Leidinger [EMAIL PROTECTED] writes:
Isn't this a property which can be set at build time? I mean: isn't
there a $OSNAME case where this can be set for a specific OS? So it
boil down to just set
In [EMAIL PROTECTED], Dag-Erling Smørgrav [EMAIL PROTECTED] typed:
Mike Meyer [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
A number of ports seem to depend on the directory tree in ${LOCALBASE}
existing - ${LOCALBASE}/man/... and ${LOCALBASE}/etc, in
particular.
Quoting Dag-Erling Smørgrav [EMAIL PROTECTED] (from Mon, 14 May 2007
14:27:33 +0200):
Alexander Leidinger [EMAIL PROTECTED] writes:
If this works well, you just have to submit this patch to the libtool
maintainers and wait until all (relevant) software packages are
updated to use the
Bert JW Regeer wrote:
On May 12, 2007, at 5:14 AM, Philippe Laquet wrote:
Stanislav Sedov a écrit :
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages
On Sat, 12 May 2007 16:26:53 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
Stanislav Sedov wrote:
I agree, that there's a lot of ready tools for parsing xml, but why
not use much simple language that can be parsed by sed or awk in few
lines?
Because of mindshare. Young people know SQL
On Sat, 12 May 2007 11:31:59 -0700
Bert JW Regeer [EMAIL PROTECTED] mentioned:
SQLite is compiled inside a program, and as such does not require any
resources other than one file handle and some CPU time when querying.
The file is stored on disk, and requires no separate process to be
running
On Sat, 12 May 2007 16:25:06 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
It's not SQL I'm interested in, it's the additional features:
- performance
- transaction safety (commit all changes or none)
- constraints (like unique keys - sqlite unfortunately doesn't support
foreign keys)
-
Roman Divacky [EMAIL PROTECTED] writes:
ruby2.0 will come with a virtual machine which should speed up things. ruby2.0
is expected soon enough (2008?)
Sure, just like Perl 6...
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
Mike Meyer [EMAIL PROTECTED] writes:
Moving the OS into the package system has been on the todo list for
a long time (assuming it's still there - there are people opposed to
that).
It has *never* been on the todo list.
How would setting LOCALBASE=/usr break this? Of course, equally valid
is
On Sun, May 13, 2007 at 08:25:55PM +0200, Dag-Erling Smrgrav wrote..
Mike Meyer [EMAIL PROTECTED] writes:
Moving the OS into the package system has been on the todo list for
a long time (assuming it's still there - there are people opposed to
that).
It has *never* been on the todo list.
Duane Whitty suggested:
I'm a little out of practice, however, perhaps the routines
that manipulate the ports meta-data could be sufficiently
agnostic about how the data is being manipulated that it
would facilitate experimentation with different
back-ends at a later time
Yes. This is
David Naylor volunteered:
Since the installation system is being tackled under a SoC project I am
hoping to give the packaging system a go.
Wonderful! Be careful about one point: The packaging system
as a whole is a big system; much bigger than many people
believe. A lot of people
In [EMAIL PROTECTED], Dag-Erling Smørgrav [EMAIL PROTECTED] typed:
Mike Meyer [EMAIL PROTECTED] writes:
Moving the OS into the package system has been on the todo list for
a long time (assuming it's still there - there are people opposed to
that).
It has *never* been on the todo list.
Jos Backus wrote:
On Fri, May 11, 2007 at 11:23:00AM -0400, Mike Meyer wrote:
[snip]
How robust is it - can a corrupt block fry the entire database?
Dunno, but Transactions are atomic, consistent, isolated, and durable (ACID)
even after system crashes and power failures.. So it appears to
On Fri, May 11, 2007 at 12:16:12PM -0700, Jos Backus wrote:
On Fri, May 11, 2007 at 01:34:07PM -0400, Mike Meyer wrote:
[snip]
How about portability - can I move the file to a completely
different architecture and still get the data from it?
[snip]
The answer (Yes) can be found in this
Jona Joachim wrote:
I don't think it would be a good idea to use SQLite for this purpose.
First of all using the file system is the Unix way of doing things. It's
efficient and easy to use, it transparent and user friendly. You can
simply run vi to inspect a text file but you can't do this
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database, and I propose all of
this be replaced by a single SQLite database. SQLite is public domain
(can
cyclic dependancies in it!), but still, in itself, I think the choice of
Ruby isn't performance-critical.
ruby2.0 will come with a virtual machine which should speed up things. ruby2.0
is expected soon enough (2008?)
___
freebsd-hackers@freebsd.org
Ivan Voras wrote:
In my (limited) experience, this sort of task should not depend much on
the speed of the language. The most CPU-intensive task portupgrade does
is resolving dependencies, and on a running system this is a DAG forest
of about 500 nodes. I know portupgrade has some highly
Stanislav Sedov a écrit :
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database, and I propose all of
this be replaced by a single SQLite database.
On Sat, 12 May 2007 14:14:39 +0200
Philippe Laquet [EMAIL PROTECTED] mentioned:
XML could be an altertative to order packages, it can be parsed with
some limited dependencies like PERL. The userland tools to manage
packages could be based on that language? It is well known by many
users,
Stanislav Sedov wrote:
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database, and I propose all of
this be replaced by a single SQLite database.
Stanislav Sedov wrote:
I agree, that there's a lot of ready tools for parsing xml, but why
not use much simple language that can be parsed by sed or awk in few
lines?
Because of mindshare. Young people know SQL and XML, but not grep.
signature.asc
Description: OpenPGP digital signature
On May 12, 2007, at 5:14 AM, Philippe Laquet wrote:
Stanislav Sedov a écrit :
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full
of text
files for storing the installed packages database, and I propose
On May 12, 2007, at 5:14 AM, Philippe Laquet wrote:
Stanislav Sedov a écrit :
On Fri, 11 May 2007 02:10:05 +0200
Ivan Voras [EMAIL PROTECTED] mentioned:
- I think it's time to give up on using BDB+directory tree full
of text
files for storing the installed packages database, and I propose
On Thursday, 10 May 2007 at 20:20:42 -0700, Garrett Cooper wrote:
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it
On Thu, 10 May 2007 22:03:22 -0400
Mike Meyer [EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
Personally, I'd still like LOCALBASE to move out of /usr/local. Maybe
it's time to reconsider
Ivan Voras [EMAIL PROTECTED] writes:
- A quick test confirms that the current bsdtar will happily ignore any
extra data at the end of a tgz/tbz archive, so package metadata can be
embedded there, thus conserving existing infrastructure and being fast
to parse. I suggest encoding this metadata
Kris Kennaway [EMAIL PROTECTED] writes:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
Personally, I'd still like LOCALBASE to move out of /usr/local. Maybe
it's time to reconsider that.
Not gonna happen as a default, but you can change it on your systems
if you like.
Not if
On Fri, May 11, 2007 at 10:19:46AM +0200, Dag-Erling Sm??rgrav wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
Personally, I'd still like LOCALBASE to move out of /usr/local. Maybe
it's time to reconsider that.
Not gonna happen
Julian Elischer wrote:
ok, let me give you some words that come from the wisdom of having done
this for 30 years.
Use an SQL DB file for this over my dead body..
:)
I certainly won't be going on a campaign for it, but...
Now having said that, I need to modify it a bit and explain.
Kris Kennaway [EMAIL PROTECTED] writes:
On Fri, May 11, 2007 at 10:19:46AM +0200, Dag-Erling Sm??rgrav wrote:
Not if you want to use pre-built packages. You made sure of that when
you decided (against my objections) to include .la files in packages.
I have a suspicion you're never going to
On Fri, May 11, 2007 at 10:33:29AM +0200, Dag-Erling Sm??rgrav wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Fri, May 11, 2007 at 10:19:46AM +0200, Dag-Erling Sm??rgrav wrote:
Not if you want to use pre-built packages. You made sure of that when
you decided (against my objections) to
On Fri, May 11, 2007 at 10:33:29AM +0200, Dag-Erling Smørgrav wrote:
We already have a mechanism for recording dependencies between
libraries; it's built into the ELF format, and does not require
hardcoding any directories. Introducing .la files which override the
existing mechanism and *do*
Kris Kennaway [EMAIL PROTECTED] writes:
On Fri, May 11, 2007 at 10:33:29AM +0200, Dag-Erling Sm??rgrav wrote:
The existence of .la files is a bug.
We already have a mechanism for recording dependencies between
libraries; it's built into the ELF format, and does not require
hardcoding
On 2007-May-11 02:10:05 +0200, Ivan Voras [EMAIL PROTECTED] wrote:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database,
Why?
and I propose all of
this be replaced by a single SQLite database.
I'll agree with Julian on this
On Fri, May 11, 2007 at 02:10:05AM +0200, Ivan Voras wrote:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database, and I propose all of
this be replaced by a single SQLite database.
Take a look at the pkgjam presentation
Kris Kennaway [EMAIL PROTECTED] writes:
On Fri, May 11, 2007 at 10:33:29AM +0200, Dag-Erling Sm??rgrav wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Fri, May 11, 2007 at 10:19:46AM +0200, Dag-Erling Sm??rgrav wrote:
Not if you want to use pre-built packages. You made sure of that
Peter Jeremy wrote:
On 2007-May-11 02:10:05 +0200, Ivan Voras [EMAIL PROTECTED] wrote:
- I think it's time to give up on using BDB+directory tree full of text
files for storing the installed packages database,
Why?
- no strict format
- slow
- not transaction safe
- harder to use then SQL
Ivan Voras [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav wrote:
Ivan Voras [EMAIL PROTECTED] writes:
You can inspect s sqlite database with the provided utility. Unless the
database gets corrupted (which it tries to avoid by respecting ACID),
ACID is not something a database respects,
Ivan Voras [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav wrote:
The world would be a much nicer place if people would stop redefining
technical terms to mean whatever suits them.
I think you're overreacting. You say: if the database is consistent,
it's ACID (Avoiding database corruption is
Ivan Voras [EMAIL PROTECTED] writes:
You can inspect s sqlite database with the provided utility. Unless the
database gets corrupted (which it tries to avoid by respecting ACID),
ACID is not something a database respects, it is a set of guarantees
that it provides to the application. Avoiding
Ivan Voras [EMAIL PROTECTED] writes:
des@ mentioned putting metadata info at the front of the file - I
don't see how this would help. The most common operation with binary
packages *over the network* is pkg_add -r, which will need to read
it whole anyway, and it would help greatly for things
Dag-Erling Smørgrav wrote:
The world would be a much nicer place if people would stop redefining
technical terms to mean whatever suits them.
I think you're overreacting. You say: if the database is consistent,
it's ACID (Avoiding database corruption is a necessary requirement for,
rather
On Fri, May 11, 2007 at 11:59:41AM +0200, Ivan Voras wrote:
I think you're overreacting. You say: if the database is consistent,
it's ACID (Avoiding database corruption is a necessary requirement for,
rather than a consequence of, ACID) and I say: if the database is ACID,
it's consistent.
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
There are a few ways you can go. The simplest is to install a
complete i386 world in e.g. /compat/ia32 and have i386 packages
installed there, and change the kernel to do a magic directory
lookup for i386 binaries that does path
Quoting Dag-Erling Smørgrav [EMAIL PROTECTED] (from Fri, 11 May 2007
10:33:29 +0200):
The existence of .la files is a bug.
I fully agree.
We already have a mechanism for recording dependencies between
libraries; it's built into the ELF format, and does not require
hardcoding any
On Fri, May 11, 2007 at 07:58:02AM -0700, Tim Kientzle wrote:
3) As DES pointed out, the package tools must be able
to read the metadata before the files. If you really
need a completely separate metadata file, make it
the second file in the archive.
Actually, the argument is pretty
Perhaps this is a good time I should mention that I think sqlite would
also be good for the password and login databases? :)
Someone has already pointed out the horror that is the Windows
registry. IIUC, even MS has figured out this is a bad idea, and gotten
away from it with Vista. But it's
Ivan Voras wrote:
- A quick test confirms that the current bsdtar will happily ignore any
extra data at the end of a tgz/tbz archive, so package metadata can be
embedded there, thus conserving existing infrastructure...
Not a good idea at all.
1) Keeping everything within the archive makes it
On Fri, May 11, 2007 at 11:23:00AM -0400, Mike Meyer wrote:
[snip]
How robust is it - can a corrupt block fry the entire database?
Dunno, but Transactions are atomic, consistent, isolated, and durable (ACID)
even after system crashes and power failures.. So it appears to try hard to
minimize
In [EMAIL PROTECTED], Jos Backus [EMAIL PROTECTED] typed:
On Fri, May 11, 2007 at 11:23:00AM -0400, Mike Meyer wrote:
[snip]
How robust is it - can a corrupt block fry the entire database?
Dunno, but Transactions are atomic, consistent, isolated, and durable (ACID)
even after system
On Friday 11 May 2007 07:35 am, Mike Meyer wrote:
I still think we ought to quit pretending that ports/packages aren't
part of BSD, and default LOCALBASE to /usr. But if changing it is
being tested, that's a big help.
Personally, this is the one thing I like *most* about BSD. There is a
On Fri, May 11, 2007 at 10:35:41AM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
There are a few ways you can go. The simplest is to install a
complete i386 world in e.g. /compat/ia32 and have i386 packages
installed there, and change the kernel to
In [EMAIL PROTECTED], Freddie Cash [EMAIL PROTECTED] typed:
On Friday 11 May 2007 07:35 am, Mike Meyer wrote:
I still think we ought to quit pretending that ports/packages aren't
part of BSD, and default LOCALBASE to /usr. But if changing it is
being tested, that's a big help.
Personally,
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
The point is that the real problem is: how do you arrange the bits on
disk, not how do you wrap that in a package system. Until you
figure out a workable on-disk arrangement for the files, questions
about packaging are not relevant.
On Fri, May 11, 2007 at 03:07:27PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
The point is that the real problem is: how do you arrange the bits on
disk, not how do you wrap that in a package system. Until you
figure out a workable on-disk
On Fri, May 11, 2007 at 01:34:07PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Jos Backus [EMAIL PROTECTED] typed:
On Fri, May 11, 2007 at 11:23:00AM -0400, Mike Meyer wrote:
[snip]
How robust is it - can a corrupt block fry the entire database?
Dunno, but Transactions are atomic,
On Friday 11 May 2007 11:34 am, Mike Meyer wrote:
In [EMAIL PROTECTED], Freddie Cash [EMAIL PROTECTED]
typed:
On Friday 11 May 2007 07:35 am, Mike Meyer wrote:
I still think we ought to quit pretending that ports/packages
aren't part of BSD, and default LOCALBASE to /usr. But if changing
On 2007-May-11 17:34:48 +0200, Joerg Sonnenberger [EMAIL PROTECTED] wrote:
On Fri, May 11, 2007 at 07:58:02AM -0700, Tim Kientzle wrote:
3) As DES pointed out, the package tools must be able
to read the metadata before the files. If you really
need a completely separate metadata file,
Ivan Voras a écrit :
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its success, and as your article
describes,
On 05/11/07 19:48, Jona Joachim wrote:
Ivan Voras a écrit :
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its
Dag-Erling Smørgrav wrote:
Ivan Voras [EMAIL PROTECTED] writes:
You can inspect s sqlite database with the provided utility. Unless the
database gets corrupted (which it tries to avoid by respecting ACID),
ACID is not something a database respects, it is a set of guarantees
that it provides
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
There are clearly other workable ideas - as I said, the linux folks
managed to make it work. But it's not an easy problem. I certainly
wouldn't suggest rebuilding the packaging system to deal with this,
except as part of a larger
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
There are clearly other workable ideas - as I said, the linux folks
managed to make it work. But it's not an easy problem. I certainly
wouldn't suggest rebuilding the packaging system to deal with this,
except as part of a larger
3) As DES pointed out, the package tools must be able
to read the metadata before the files.
Actually, the argument is pretty weak. Being able to extract them
streamable and access the meta-data easily is fine. The remote access
argument is very weak as it doesn't allow e.g. signature checks.
On Sat, May 12, 2007 at 12:55:44AM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
There are clearly other workable ideas - as I said, the linux folks
managed to make it work. But it's not an easy problem. I certainly
wouldn't suggest rebuilding the
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
But you said you were interested in working on it...so what is your
idea?
Actually, I said it's on my list of things to do.
You might have meant this, but to quote what you actually said:
--
But hey, if there's a document
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its success, and as your article
describes, the installation and packaging system is
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its success, and as your article
describes, the installation and
Ivan Voras wrote:
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its success, and as your article
describes, the
In [EMAIL PROTECTED], Ivan Voras [EMAIL PROTECTED] typed:
I cannot currently actively participate in implementing proposed things,
but I can give advice on sqlite, database and xml schemas if anyone
wants to...
One of the things that would be nice for a replacement to do would be
to correctly
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Ivan Voras [EMAIL PROTECTED] typed:
I cannot currently actively participate in implementing proposed things,
but I can give advice on sqlite, database and xml schemas if anyone
wants to...
One of the things
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Ivan Voras [EMAIL PROTECTED] typed:
I cannot currently actively participate in implementing proposed things,
but I can give advice on sqlite,
On Thu, May 10, 2007 at 10:03:22PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Ivan Voras [EMAIL PROTECTED] typed:
I cannot currently actively participate in
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 10:03:22PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Ivan Voras [EMAIL
David Naylor wrote:
Dear Jordan
Recently I stumbled across a document you wrote in 2001, entitled FreeBSD
installation and package tools, past, present and future. I find FreeBSD
appealing and I would like to contribute it its success, and as your article
describes, the installation and
On Thu, May 10, 2007 at 11:15:37PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 10:03:22PM -0400, Mike Meyer wrote:
In [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] typed:
On Thu, May 10, 2007 at 09:47:49PM -0400, Mike
86 matches
Mail list logo
