On Jun 2, 2012, at 00:51, Daniel Kalchev wrote:
On 02.06.2012, at 07:19, Freddie Cash fjwc...@gmail.com wrote:
Glustre sits above the storage system, replicating data between systems.
So, disks -- ZFS (via Zvols) -- Glustre.
How is this different than ZFS using remote zvols via
Am Freitag, den 01.06.2012, 13:56 -0400 schrieb Michael R. Wayne:
On Fri, Jun 01, 2012 at 05:03:26AM -0700, Mehmet Erol Sanliturk wrote:
If you are NOT using FreeBSD for any area or some areas , would you please
list those areas with most important first to least important last ?
As
On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
wrote:
Hi,
On 30 May 2012 PM 7:20:31 David Chisnall wrote:
This is off-topic, so please feel free to disregard it, but I'm sending
it to this list in the hope that it will reach a largish number of users.
I am
On Fri, Jun 01, 2012 at 05:12:14PM -0700, Dave Hayes wrote:
1) I don't use FreeBSD for virtualization as the host OS. I really want
to, becaus I want to be able to somewhat trust the kernel hosting my
virtual machines. FreeBSD technology, support, and documentation for
this idea appears
On 06/01/12 21:46, Lars Engels wrote:
On Fri, Jun 01, 2012 at 08:32:08PM +0100, Chris Rees wrote:
On 1 June 2012 16:20, Nomen Nescio nob...@dizum.com wrote:
Dear All ,
There is a thread
Why Are You Using FreeBSD ?
I think another thread with the specified subject 'Why Are You NOT Using
Hi,
On 02 June 2012 AM 9:14:28 Chris Rees wrote:
On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
wrote:
But I have to mention one disadvantage. The ports are in no way linked to
the releases. This leads to situations in which a small change in a basic
library will
On 02.06.12 09:23, David Magda wrote:
On Jun 2, 2012, at 00:51, Daniel Kalchev wrote:
On 02.06.2012, at 07:19, Freddie Cashfjwc...@gmail.com wrote:
Glustre sits above the storage system, replicating data between systems.
So, disks -- ZFS (via Zvols) -- Glustre.
How is this different
On 2 Jun 2012, at 03:56, Erich Dollansky wrote:
But I have to mention one disadvantage. The ports are in no way linked to the
releases. This leads to situations in which a small change in a basic library
will result in a complete update of the installed ports. I expressed this
already many
On 02.06.12 12:27, O. Hartmann wrote:
1a) On scietific production systems, FreeBSD has been banned due to
the lack of HPC compilers and appropriate mathematical libraries. The
lack of professional/academic support, like that from NAG in the late
1990s, has been droped for FreeBSD as well as
Hi,
On 02 June 2012 AM 11:39:16 David Chisnall wrote:
On 2 Jun 2012, at 03:56, Erich Dollansky wrote:
But I have to mention one disadvantage. The ports are in no way linked to
the releases. This leads to situations in which a small change in a basic
library will result in a complete
On Fri, Jun 01, 2012 at 09:19:15PM -0700, Freddie Cash wrote:
Pardon my ignorance to not knowing what gluster is, but is this
conceptually similar to HAST?
Similar in concept, but different layers in the storage stack.
HAST sits between the physical disks and the filesystem, replicating
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security fixes
just to have a system which is up and running fast after I tried an upgrade
like what is happening at the moment with PNG dependent ports.
You have this already. Just install
On 02.06.12 10:21, Marc Santhoff wrote:
Am Freitag, den 01.06.2012, 13:56 -0400 schrieb Michael R. Wayne:
On Fri, Jun 01, 2012 at 05:03:26AM -0700, Mehmet Erol Sanliturk wrote:
If you are NOT using FreeBSD for any area or some areas , would you please
list those areas with most important
Hi,
On 02 June 2012 PM 12:04:26 David Chisnall wrote:
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security fixes
just to have a system which is up and running fast after I tried an upgrade
like what is happening at the moment with
On 02.06.12 12:42, Erich Dollansky wrote:
On 02 June 2012 AM 9:14:28 Chris Rees wrote:
On Jun 2, 2012 4:04 AM, Erich Dollanskyer...@alogreentechnologies.com
wrote:
But I have to mention one disadvantage. The ports are in no way linked to
the releases. This leads to situations in which a
On 2 Jun 2012, at 12:19, Erich wrote:
Hi,
On 02 June 2012 PM 12:04:26 David Chisnall wrote:
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security fixes
just to have a system which is up and running fast after I tried an upgrade
like
On Sunday, May 27, 2012 06:43:43 PM Sean Bruno wrote:
I'm trying to understand the newbus and acpi interactions on this Dell
R620 that result in the Broadcom adapter board being probed backwards
or just plain out of order in comparison to the connector layout and the
linux tg3 driver.
We
Hi,
On 02 June 2012 PM 12:50:16 David Chisnall wrote:
On 2 Jun 2012, at 12:19, Erich wrote:
Hi,
On 02 June 2012 PM 12:04:26 David Chisnall wrote:
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security
fixes just to have a
Hi,
On 02 June 2012 PM 2:53:48 Daniel Kalchev wrote:
You don't have to use the (arguable old) 'release' ports tree. Ports get
fixed/adapted for the new version usually months after release.
I think we are talking here about two totally different problems. Your hint
with sysinstall would
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving during the
release period. This could be used to give a fall back solution.
Or do I see this really too simple?
The ports tree is a moving target during release periods still, although
there
I'll try to be short.
I'm using FreeBSD both at servers and as a desktop, but I see
struggling of my friends with it in some things.
1. Ports mess. You can very easily render system unusable, or broken
if you trying to use latest ports. And then you had to became a port
master to fix all. Of
TB --- 2012-06-02 10:02:07 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-06-02 10:02:07 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-06-02
TB --- 2012-06-02 10:34:13 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-06-02 10:34:13 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-06-02
On 06/02/12 14:47, Daniel Kalchev wrote:
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving
during the release period. This could be used to give a fall back
solution.
Or do I see this really too simple?
The ports tree is a moving target
On 1-6-2012 20:57, Thomas David Rivers wrote:
We used to have FreeBSD exclusively on desktops...
Now, we have migrated to other desktops (mac) with FreeBSD running
the build and file server...
Why?
Because - the mac updates itself! No pain, no installation,
no keeping-up with mailing
Have you also recompiled nmap after you installed libpcap. Sorrry this
should be a neccesary step.
Thanks! After recompiling nmap is starting succesfully!
Thank you for your help!
___
freebsd-stable@freebsd.org mailing list
Because... at some point it may return to normal without all the
bikeshedding and, I run because, I don't run because.
The previous threads before this message should have been on a web form
or questions@ as they are completely out of control.
--
- (2^(N-1))
--- Sab 2/6/12, O. Hartmann ohart...@zedat.fu-berlin.de ha scritto:
Since I'm with FreeBSD, StarOffice, OpenOffice and even now
LibreOffice is a MESS! ...
Can you be more specific about what is wrong with
Apache OpenOffice?
best regards,
Pedro.
On Jun 2, 2012 3:19 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
On 06/02/12 14:47, Daniel Kalchev wrote:
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving
during the release period. This could be used to give a fall back
[Reply-To: advocacy@]
Jason Hellenthal wrote:
The previous threads before this message should have been on a web form
or questions@ as they are completely out of control.
Assuming you are referring to the recent Why I (don't) use FreeBSD
threads:
Thank you, I agree. I read the first couple
On Jun 2, 2012, at 1:31 PM, Chris Rees wrote:
On Jun 2, 2012 3:19 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
On 06/02/12 14:47, Daniel Kalchev wrote:
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving
during the release period.
On Sat, Jun 02, 2012 at 14:11:06 -0400 , Paul Mather wrote:
I'm not sure what the solution is for the end user. I know I get
somewhat leery of updating my ports if I see a large number of changes
coming via portsnap (like the 4000+ that accompanied the recent libpng
upgrade) and there is
Hi!
The point he made was actually not a matter of people not reading
UPDATING but that UPDATING is oftentimes not updated until after
the disruptive/potentially dangerous change has already hit the
ports tree.
I'm not sure what the solution is for the end user.
We have our reference
Hi!
For example if one wants an e-mail server, that is better
served in the long run by IMAP+MTA than any form of Exchange, because
you are not tied to one single platform and that vendor's lunacy.
In the field, many customers are drawn into the world of
Exchange and related technologies
On 2 June 2012 10:42, Erich Dollansky er...@alogreentechnologies.com wrote:
Hi,
On 02 June 2012 AM 9:14:28 Chris Rees wrote:
On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
wrote:
But I have to mention one disadvantage. The ports are in no way linked to
the
TB --- 2012-06-02 19:20:18 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-06-02 19:20:18 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-06-02
TB --- 2012-06-02 19:55:20 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-06-02 19:55:20 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-06-02
You wrote:
On Fri, Jun 01, 2012 at 05:20:39PM +0200, Nomen Nescio wrote:
Maybe FreeBSD should consider migrating to pkgsrc?
I'm not arguing that your other points are invalid (in particular,
I agree that the xorg change was really painful, and for a long time
amd64 lagged i386 badly), but
Hi,
On 02 June 2012 PM 3:47:27 Daniel Kalchev wrote:
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving during
the release period. This could be used to give a fall back solution.
Or do I see this really too simple?
The ports tree is
On Sun, Jun 03, 2012 at 01:43:43AM +0200, Fritz Wuehler wrote:
So there could be lots of overlap and just looking at the two numbers
you posted doesn't really tell the whole story.
No, I agree that it doesn't. I was just trying to add an aside, and
point out that the task would not be trivial.
Hi,
On 02 June 2012 PM 4:07:23 Alexander Yerenkow wrote:
I'll try to be short.
I'm using FreeBSD both at servers and as a desktop, but I see
struggling of my friends with it in some things.
1. Ports mess. You can very easily render system unusable, or broken
if you trying to use latest
Hi,
On 02 June 2012 PM 4:18:45 O. Hartmann wrote:
On 06/02/12 14:47, Daniel Kalchev wrote:
On 02.06.12 15:32, Erich wrote:
I know that the ports tree is a moving target. But it stops moving
during the release period. This could be used to give a fall back
solution.
Or do I see this
Hi,
On 02 June 2012 PM 2:56:01 Chris Nehren wrote:
On Sat, Jun 02, 2012 at 14:11:06 -0400 , Paul Mather wrote:
I'm not sure what the solution is for the end user. I know I get
somewhat leery of updating my ports if I see a large number of changes
coming via portsnap (like the 4000+ that
Hi,
On 02 June 2012 PM 9:50:22 Kurt Jaeger wrote:
Hi!
The point he made was actually not a matter of people not reading
UPDATING but that UPDATING is oftentimes not updated until after
the disruptive/potentially dangerous change has already hit the
ports tree.
I'm not sure what
Hi,
On 02 June 2012 PM 10:52:48 Chris Rees wrote:
On 2 June 2012 10:42, Erich Dollansky er...@alogreentechnologies.com wrote:
On 02 June 2012 AM 9:14:28 Chris Rees wrote:
On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
wrote:
But I have to mention one
45 matches
Mail list logo
