On Mon, 2 Jul 2012 21:25:58 +0300
nickolas...@gmail.com wrote:
> >> Hmm, in my local testing we've been able to use the 40G mlxen(4)
> >> adapters fine with the OFED stack. I believe we have also done a
> >> bit more involved testing on the IB side than just ping as well
> >> (at least RX and TX
>> Hmm, in my local testing we've been able to use the 40G mlxen(4)
>> adapters fine with the OFED stack. I believe we have also done a bit
>> more involved testing on the IB side than just ping as well (at least
>> RX and TX of UDP packets).
>>
> Well, it didn't work for us. We have the connext3
On Mon, 2 Jul 2012 13:52:25 -0400
John Baldwin wrote:
> On Monday, July 02, 2012 1:23:29 pm Gergely CZUCZY wrote:
> > On Mon, 2 Jul 2012 10:55:04 -0400
> > John Baldwin wrote:
> >
> > > On Friday, June 29, 2012 5:50:05 am Gergely CZUCZY wrote:
> > > > Hello,
> > > >
> > > > I'm mostly using fr
On Monday, July 02, 2012 1:23:29 pm Gergely CZUCZY wrote:
> On Mon, 2 Jul 2012 10:55:04 -0400
> John Baldwin wrote:
>
> > On Friday, June 29, 2012 5:50:05 am Gergely CZUCZY wrote:
> > > Hello,
> > >
> > > I'm mostly using freebsd, but there are a few cases where it's
> > > impossible to do, and
On Mon, 2 Jul 2012 10:55:04 -0400
John Baldwin wrote:
> On Friday, June 29, 2012 5:50:05 am Gergely CZUCZY wrote:
> > Hello,
> >
> > I'm mostly using freebsd, but there are a few cases where it's
> > impossible to do, and because of these, i'm not using fbsd there.
> >
> > These reasons are mos
On Friday, June 29, 2012 5:50:05 am Gergely CZUCZY wrote:
> Hello,
>
> I'm mostly using freebsd, but there are a few cases where it's
> impossible to do, and because of these, i'm not using fbsd there.
>
> These reasons are mostly are:
> - Lack of a working infiniband/OFED stack, with all its ut
> Yes, virtualbox is not that bad. However, to get some really nice
> features, you need the non-free version. Also, we can use citrix's
> xenserver's management tool to manage non-citrix xen clusters, because
> the API is same. With that we get a management tool for our clusters,
> which is really
On Fri, 29 Jun 2012 10:55:20 +0100
Pete French wrote:
> > - Lack of proper support for a decent hypervisor for
> > virtualisation. We can't make a hypervisor out of freebsd, if there
> > are no such virtualisations available like XEN, kvm or something
> > similar, that just works out of the box.
> - Lack of proper support for a decent hypervisor for virtualisation.
>We can't make a hypervisor out of freebsd, if there are no such
>virtualisations available like XEN, kvm or something similar, that
>just works out of the box.
What do you need that VirtualBox doesn't provide ? I
Hello,
I'm mostly using freebsd, but there are a few cases where it's
impossible to do, and because of these, i'm not using fbsd there.
These reasons are mostly are:
- Lack of a working infiniband/OFED stack, with all its utils,
mellanox connectX3 drivers, RDMA, iscsi-over-RDMA, nfs-over-RDMA
On Fri, Jun 01, 2012 at 04:09:53PM -0400, Chris Nehren wrote:
> On Fri, Jun 01, 2012 at 14:50:22 -0500 , Bryan Drewery wrote:
> > FWIW, there is freebsd-update(8) now for binary updating of base, and
> > pkgng[1] will allow binary upgrading of packages/ports similar to apt-get.
> >
> > [1] http://
On Tuesday 12 June 2012 07:10 Chris Rees wrote:
>
> > are essential for a desktop to work properly
> >
> > of course the package collection needs then something similar to
>
> portversion,
>
> > but not based on ports tree versions, in order to find available updates
> >
> > who then wants to
On Jun 12, 2012 10:48 AM, "H" wrote:
>
> On Monday 11 June 2012 20:59 Chuck Swiger wrote:
> > Hi, Dave--
> >
> > On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote:
> > [ ... ]
> >
> > > Do I have this wrong? Anyone see a problem with this picture?
> > > What can we do to "just upgrade" in a safe fashi
On Monday 11 June 2012 20:59 Chuck Swiger wrote:
> Hi, Dave--
>
> On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote:
> [ ... ]
>
> > Do I have this wrong? Anyone see a problem with this picture?
> > What can we do to "just upgrade" in a safe fashion when we want to?
>
> Two things help tremendously:
In message <7b6e5361-b109-498e-b22f-96a94dec3...@mac.com>, Chuck Swiger writes:
> Hi, Dave--
>
> On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote:
> [ ... ]
> > Do I have this wrong? Anyone see a problem with this picture?
> > What can we do to "just upgrade" in a safe fashion when we want to?
>
>
On Jun 12, 2012, at 2:41 AM, grenville armitage wrote:
>
>
>> Rainer Duffner writes:
> [..]
>>> Personally, I don't need more frequent FreeBSD-releases but two or
>>> maybe three ports-tree freezes per year would be good.
>
> Perhaps not so much freezes per se, but if there are particul
Hi, Dave--
On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote:
[ ... ]
> Do I have this wrong? Anyone see a problem with this picture?
> What can we do to "just upgrade" in a safe fashion when we want to?
Two things help tremendously:
#1: Have working backups. If you run into a problem, roll back t
Adam Strohl writes:
> There in lies the question -- why do you need to compile a port which
> was just released? Is it a security thing or is it "I want the latest"
> ? I'm just curious (and totally uninterested in how this ranks in your
> "worse question" list).
If I weren't honorable, I'd
Rainer Duffner writes:
[..]
Personally, I don't need more frequent FreeBSD-releases but two or
maybe three ports-tree freezes per year would be good.
Perhaps not so much freezes per se, but if there are particular
dates at which the ports tree is known to compile properly (for
some
[ This probably should be redirected to freebsd-ports but I am not
subscribed so the anal mailer will likely reject such a submission ]
Rainer Duffner writes:
> Am 06.06.2012 um 20:59 schrieb Dave Hayes:
>> I believe this is the first time I've seen more documentation labeled as
>> "extraneous"
O. Hartmann writes:
> >> Among all the default problems with ports, libreoffice[1] adds to the
> >> group of annoyances[2] at the moment. I don't know when I have seen
> >> "portmaster -ad" run through successfully last time. I need more and
> >> more "-x" options to exclude ports which fail
On 06/10/12 19:20, Chris Rees wrote:
> On 10 June 2012 18:10, O. Hartmann wrote:
>> On 06/10/12 17:43, John Merryweather Cooper wrote:
>>> On 06/10/12 09:54, Martin Sugioarto wrote:
Am Sun, 10 Jun 2012 11:37:09 +0100
schrieb Chris Rees:
> Er... people always test their commits.
On 10 June 2012 18:10, O. Hartmann wrote:
> On 06/10/12 17:43, John Merryweather Cooper wrote:
>> On 06/10/12 09:54, Martin Sugioarto wrote:
>>> Am Sun, 10 Jun 2012 11:37:09 +0100
>>> schrieb Chris Rees:
>>>
Er... people always test their commits. Sometimes edge cases will
creep in, suc
On 06/10/12 17:43, John Merryweather Cooper wrote:
> On 06/10/12 09:54, Martin Sugioarto wrote:
>> Am Sun, 10 Jun 2012 11:37:09 +0100
>> schrieb Chris Rees:
>>
>>> Er... people always test their commits. Sometimes edge cases will
>>> creep in, such as the libreoffice failure which was due to diffe
John Merryweather Cooper wrote:
> On 06/10/12 09:54, Martin Sugioarto wrote:
> > [...]
> > - It would be nice to have a mechanism that tells you that your perl,
> >mysql or whatever is not the default version anymore and you should
> >consider updating to the default (and recommended)
On 06/10/12 09:54, Martin Sugioarto wrote:
Am Sun, 10 Jun 2012 11:37:09 +0100
schrieb Chris Rees:
Er... people always test their commits. Sometimes edge cases will
creep in, such as the libreoffice failure which was due to different
configurations, but to suggest that the commit wasn't tested
Am Sun, 10 Jun 2012 11:37:09 +0100
schrieb Chris Rees :
> Er... people always test their commits. Sometimes edge cases will
> creep in, such as the libreoffice failure which was due to different
> configurations, but to suggest that the commit wasn't tested is quite
> frankly insulting-- it built
Hi,
On 08 June 2012 13:34:46 Steve Franks wrote:
> has been running 7.x for years, and shows no sign of giving out. Just
> keep sticking new HDD's in periodically. For a server that you rarely
> add new apps to, it's stellar. Mind you, it's probably chock full of
> security holes due to it's age.
On 10 June 2012 11:51, O. Hartmann wrote:
> On 06/10/12 12:37, Chris Rees wrote:
>> On 10 June 2012 11:12, Martin Sugioarto wrote:
>>> Am Sat, 09 Jun 2012 21:09:09 +0700
>>> schrieb Adam Strohl :
>>>
I get the feeling people are updating their ports tree and then
recompiling/reinstallin
On 06/10/12 12:37, Chris Rees wrote:
> On 10 June 2012 11:12, Martin Sugioarto wrote:
>> Am Sat, 09 Jun 2012 21:09:09 +0700
>> schrieb Adam Strohl :
>>
>>> I get the feeling people are updating their ports tree and then
>>> recompiling/reinstalling everything "just because" and then are
>>> compla
On 10 June 2012 11:12, Martin Sugioarto wrote:
> Am Sat, 09 Jun 2012 21:09:09 +0700
> schrieb Adam Strohl :
>
>> I get the feeling people are updating their ports tree and then
>> recompiling/reinstalling everything "just because" and then are
>> complaining when one thing breaks (its the only thi
Am Sat, 09 Jun 2012 21:09:09 +0700
schrieb Adam Strohl :
> I get the feeling people are updating their ports tree and then
> recompiling/reinstalling everything "just because" and then are
> complaining when one thing breaks (its the only thing I can think of).
Hi.
But it does not need to brea
On 6/9/2012 21:36, H wrote:
why is there an update, would be a little bit better
My point was why do you need the update, and can't wait until its been
better vetted. The porters do the best they can but can't test everything.
but a real good question would be, why is there a not working/c
Adam Strohl wrote:
> On 6/9/2012 3:34, Steve Franks wrote:
>> Every time libjpeg or
>> perl or python bumps the rev, I have to explain to my boss that I
>> won't be using my computer for 48 hours.
>
> Why is this? And why are you updating every time there is a rev bump?
>
certainly the worse qu
On 6/9/2012 21:04, O. Hartmann wrote:
Well, this is a good question. Unfortunately, I did an update of the
ports tree and PNG update rushed in. The information in UPDATING came a
in bit later, but since then several ports have been updated already -
and rendered some applications unuseable.
The
On 06/09/12 15:43, Adam Strohl wrote:
> On 6/9/2012 14:50, O. Hartmann wrote:
>> Lucky man! We are "off" from some desktop services (like LibreOffice and
>> Firefox) for more than a week now!
>
> Why did you update to begin with? Bug/security fix?
>
> --
> Adam Strohl
> http://www.ateamsystems.
On 6/9/2012 14:50, O. Hartmann wrote:
Lucky man! We are "off" from some desktop services (like LibreOffice and
Firefox) for more than a week now!
Why did you update to begin with? Bug/security fix?
--
Adam Strohl
http://www.ateamsystems.com/
___
fre
On 06/09/12 06:45, Adam Strohl wrote:
> On 6/9/2012 3:34, Steve Franks wrote:
>> Every time libjpeg or
>> perl or python bumps the rev, I have to explain to my boss that I
>> won't be using my computer for 48 hours.
Lucky man! We are "off" from some desktop services (like LibreOffice and
Firefox)
On 6/9/2012 3:34, Steve Franks wrote:
Every time libjpeg or
perl or python bumps the rev, I have to explain to my boss that I
won't be using my computer for 48 hours.
Why is this? And why are you updating every time there is a rev bump?
It almost sounds like you're recompiling everything just
I think XOrg 7.2 or 7.3 or whatever was the straw that broke the
camel's back for me, but it's just an example. Every time libjpeg or
perl or python bumps the rev, I have to explain to my boss that I
won't be using my computer for 48 hours. You can say "don't follow the
bleeding edge", but it seem
On Fri, Jun 1, 2012 at 8:43 AM, Pierre-Luc Drouin wrote:
> For me it is the lack of support for suspend/resume on laptops. I don't
> want to turn off my laptop when I am in the middle of doing something but
> need to put the laptop aside. I love using FreeBSD on servers, workstations
> and even a
Am 06.06.2012 um 20:59 schrieb Dave Hayes:
>
>
> I believe this is the first time I've seen more documentation labeled as
> "extraneous". :) I had thought to suggest an implementation by having a
> simple pkg-option-desr file which describes the options and implications
> in each port. Are you s
David Magda wrote:
> On Jun 1, 2012, at 21:03, Chris Nehren wrote:
>
> > You say your'e using ZVOLs but then recommend gluster for large
> > filesystems. I would like to take a moment to point out that one of
> > the
> > design goals of ZFS was to scale beyond the capabilities of current
> > hardw
Phil Regnauld wrote:
> David Magda (dmagda) writes:
> > On Jun 1, 2012, at 09:12, Phil Regnauld wrote:
> >
> > > * Gluster
> > >
> > > For very large FSes, nothing beats it, especially now that 3.3
> > > has been
> > > released.
> >
> > Isilon built their OneFS on top of FreeBSD, does that co
Hi,
On 06 June 2012 17:40:28 Rick Miller wrote:
> I, for one, appreciate you changing the subject because I didn't know
> this either and its an important function in my use case where point
> in time snapshots are important to the architects and ops folks!
>
and it should be mentioned in the ha
On 6 Jun 2012, at 23:10, grenville armitage wrote:
>
>
> On 06/07/2012 00:16, Chris Rees wrote:
>> On 6 June 2012 14:12, Erich wrote:
>[..]
>
>>> is my English really this bad?
>>>
>>> From the handbook:
>>>
>>> '. In particular, use only tag=. for the ports-* collections.'
>>
>> Your
I, for one, appreciate you changing the subject because I didn't know
this either and its an important function in my use case where point
in time snapshots are important to the architects and ops folks!
On 6/6/12, grenville armitage wrote:
>
>
> On 06/07/2012 00:16, Chris Rees wrote:
>> On 6 Jun
On 06/07/2012 00:16, Chris Rees wrote:
On 6 June 2012 14:12, Erich wrote:
[..]
is my English really this bad?
From the handbook:
'. In particular, use only tag=. for the ports-* collections.'
Your English is fine, but "being told to use tag=." != "tag=. is the
only tag that exi
On Tue, 5 Jun 2012, Mark Linimon wrote:
It's not particularly easy to see this on cvsweb. But let's take a look
at a random Mk/bsd.*.mk file via 'cvs log':
RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v
Working file: bsd.apache.mk
head: 1.36
branch:
locks: strict
access list:
sy
Daniel Kalchev writes:
> On 04.06.12 22:32, Dave Hayes wrote:
>> That's a fair position. Perhaps it would not be too much trouble to add
>> this one idea to optionsng: a "more info" field on each option knob
>> which may be filled in by a port maintainer.
> The pkg-descr file in the port already c
On 6 June 2012 14:12, Erich wrote:
> Hi,
>
> On 06 June 2012 8:48:10 Chris Rees wrote:
>> On Jun 6, 2012 3:38 AM, "Erich" wrote:
>> >
>
>> No it doesn't. It states clearly that you shouldn't use tags unless you
>> know what you are doing, as several of us have explained more than once.
>>
> is my
Hi,
On 06 June 2012 8:48:10 Chris Rees wrote:
> On Jun 6, 2012 3:38 AM, "Erich" wrote:
> >
> No it doesn't. It states clearly that you shouldn't use tags unless you
> know what you are doing, as several of us have explained more than once.
>
is my English really this bad?
>From the handbook:
Hi,
let me rite the answer on top before my mouse scrolling down.
I am fully aware of what you are writing. I am saying this from the point of
view people have when they start with FreeBSD.
This little help would make them feel much much saver.
I know that it would not change much in real life
On 06/06/12 10:41, Nicolas Rachinsky wrote:
> * "O. Hartmann" [2012-06-03 22:55 +0200]:
>> ... I spent now two complete days watching my boxes updating their
>> ports. Several ports do not compile anymore (inkscape, libreoffice,
>> libxul, to name some of the very hurting ones!).
>
> Do you have
* "O. Hartmann" [2012-06-03 22:55 +0200]:
> ... I spent now two complete days watching my boxes updating their
> ports. Several ports do not compile anymore (inkscape, libreoffice,
> libxul, to name some of the very hurting ones!).
Do you have graphics/libwpg01 installed? After deinstalling this,
On Jun 6, 2012 3:38 AM, "Erich" wrote:
>
> Hi,
>
> On 05 June 2012 7:13:47 Mark Linimon wrote:
> > On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote:
> > > But is this true for apache only or for the whole ports tree?
> >
> > Entire tree.
>
> my problem with this is that the documentation stat
On 06.06.12 05:28, Erich wrote:
Why should a normal user continue to search for a tag when the
handbook is so clear on this? Erich
I continue to wonder, why are you searching for tags on the ports tree,
when you were told on a number of occasions that those who depend on
particular state of
In message <1805884.wjzbqif...@x220.ovitrap.com>, Erich writes:
> Hi,
>
> On 06 June 2012 0:42:47 Mark Andrews wrote:
> >
> > In message <1541214.zfrdxxb...@x220.ovitrap.com>, Erich writes:
> > > Hi,
> > >
> > > On 05 June 2012 1:09:50 Mark Linimon wrote:
> > > > On Tue, Jun 05, 2012 at 01:00:4
Hi,
On 06 June 2012 0:42:47 Mark Andrews wrote:
>
> In message <1541214.zfrdxxb...@x220.ovitrap.com>, Erich writes:
> > Hi,
> >
> > On 05 June 2012 1:09:50 Mark Linimon wrote:
> > > On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> > > > All of these, with the exception of HEAD (which is
Hi,
On 05 June 2012 7:13:47 Mark Linimon wrote:
> On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote:
> > But is this true for apache only or for the whole ports tree?
>
> Entire tree.
my problem with this is that the documentation states something very different:
>From the handbook at the l
Hi,
On 05 June 2012 1:09:50 Mark Linimon wrote:
> On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> > All of these, with the exception of HEAD (which is always a valid tag),
> > only apply to the src/ tree. The ports/, doc/, and www/ trees are not
> > branched.
>
> If you create a branch,
On Fri, 01 Jun 2012 20:57:52 +0200, 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
> Look at the comment of the maintainer of LibreOffice ...
btw I tested and libreoffice is still working as expected.
Most of the time the libreoffice failures is from people tuning their system
without knowing the impact/risk of doing such, for example building some c++
libraries with g++47 let'
Mark Linimon wrote:
> The current status is that we support 8.x and 9.x well. Ports support
> for 7.x is starting to fade over time as new upstream releases rely
> on newer APIs. 6.x went EOL 11/30/2010 and we no longer claim to
> support it in ports.
FWIW ... In fact, I can confirm that t
In message <1541214.zfrdxxb...@x220.ovitrap.com>, Erich writes:
> Hi,
>
> On 05 June 2012 1:09:50 Mark Linimon wrote:
> > On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> > > All of these, with the exception of HEAD (which is always a valid tag),
> > > only apply to the src/ tree. The por
O. Hartmann wrote:
> 2) Disk and network I/O issues under load. We realized that FreeBSD has
> some issues in multithreaded environments. Even on 6/12 or 12/24
> core/thread systems, under heavy load (especially network and CPU load),
> disk I/O was (is?) poor. This is a no-go in a HPC environ
Hi,
On 05 June 2012 1:09:50 Mark Linimon wrote:
> On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> > All of these, with the exception of HEAD (which is always a valid tag),
> > only apply to the src/ tree. The ports/, doc/, and www/ trees are not
> > branched.
>
> If you create a branch,
On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote:
> But is this true for apache only or for the whole ports tree?
Entire tree.
mcl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
On Jun 5, 2012 3:07 AM, "Erich" wrote:
>
> Hi,
>
> On 05 June 2012 11:24:25 Mark Andrews wrote:
> >
>
> > Version tagging is just a convient way to get a snapshot at a
> > particular point in time unless you create branches that are them
>
> we do not ask for more. There should be only one differe
Hi,
On 05 June 2012 1:09:50 Mark Linimon wrote:
> On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> > All of these, with the exception of HEAD (which is always a valid tag),
> > only apply to the src/ tree. The ports/, doc/, and www/ trees are not
> > branched.
>
> If you create a branch,
Hi,
On 05 June 2012 1:01:37 Mark Linimon wrote:
> On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote:
> > I did not know this. Do you have a link for this? I never read about it.
>
> The EOL announcements have them. I don't think the release announcements
> do, however.
>
this is the problem
On 05.06.12 07:33, Zane C. B-H. wrote:
[on Exchange wiping devices]
From a enterprise perspective, it makes sense. Lets say a device goes
missing, it allows one to wipe it the next time it calls home.
This is supposed to be handled by the device management software. Not by
your e-mail serv
On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote:
> All of these, with the exception of HEAD (which is always a valid tag),
> only apply to the src/ tree. The ports/, doc/, and www/ trees are not
> branched.
If you create a branch, you must create a tag for that branch.
However, you can crea
On 04.06.12 22:32, Dave Hayes wrote:
Chris Nehren writes:
The descriptions of the options assume the admin is familiar with the
software they're installing. I do not think it is the FreeBSD Project's
purview to document every option for every port. At the very least it'd
take quite a lot of t
On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote:
> I did not know this. Do you have a link for this? I never read about it.
The EOL announcements have them. I don't think the release announcements
do, however.
mcl
___
freebsd-stable@freebsd.org m
Hi,
On 05 June 2012 15:33:16 Mark Andrews wrote:
>
> In message <2490439.ec638ti...@x220.ovitrap.com>, Erich writes:
> > Hi,
> >
> > On 05 June 2012 12:48:20 Mark Andrews wrote:
> > >
> > > In message <3506767.fvm2kmt...@x220.ovitrap.com>, Erich writes:
> > > >
> > > > On 05 June 2012 11:24:25
In message <2490439.ec638ti...@x220.ovitrap.com>, Erich writes:
> Hi,
>
> On 05 June 2012 12:48:20 Mark Andrews wrote:
> >
> > In message <3506767.fvm2kmt...@x220.ovitrap.com>, Erich writes:
> > >
> > > On 05 June 2012 11:24:25 Mark Andrews wrote:
> > > >
> > >
> >
> > It's already there. I
Hi,
On 05 June 2012 12:48:20 Mark Andrews wrote:
>
> In message <3506767.fvm2kmt...@x220.ovitrap.com>, Erich writes:
> >
> > On 05 June 2012 11:24:25 Mark Andrews wrote:
> > >
> >
>
> It's already there. If you want the ports as of FreeBSD 4.x EOL
> then the tag is "RELEASE_4_EOL". If you w
On Mon, 04 Jun 2012 18:49:45 +0300
Daniel Kalchev wrote:
>
>
> On 04.06.12 18:04, xenophon\+freebsd wrote:
> >> -Original Message-
> >> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> >> sta...@freebsd.org] On Behalf Of Daniel Kalchev
> >> Sent: Saturday, June 02, 2012 1
> One doesn't have to live at the bleeding edge with ports if one
> doesn't want to even when compiling. One can live a day, a week,
> a month behind the bleeding edge and allow other to hit problems
> and report them.
To be pedantic, there's a lot of difference between reporting problems,
and su
In message <3506767.fvm2kmt...@x220.ovitrap.com>, Erich writes:
> Hi,
>
> On 05 June 2012 11:24:25 Mark Andrews wrote:
> >
>
> > Version tagging is just a convient way to get a snapshot at a
> > particular point in time unless you create branches that are them
>
> we do not ask for more. There
Hi,
On 05 June 2012 11:24:25 Mark Andrews wrote:
>
> Version tagging is just a convient way to get a snapshot at a
> particular point in time unless you create branches that are them
we do not ask for more. There should be only one difference to a snapshot. As
snapshot has a date. No matter in
In message <4fcd23fe.20...@zedat.fu-berlin.de>, "O. Hartmann" writes:
> Well, and repeatedly (no offense!) I will point out in this case, that I
> was FORCED having the latest software by the ports system!
> That it a difference in having running FreeBSD CURRENT on my own risk,
> or FreeBSD-STABLE
On 04 June 2012 16:24:56 Chris Rees wrote:
> On 3 June 2012 21:55, O. Hartmann wrote:
> > On 06/03/12 15:29, Erich wrote:
> >> Hi,
> >>
> >> On 03 June 2012 PM 5:14:10 Adam Strohl wrote:
> >>> On 6/3/2012 11:14, Erich wrote:
> What I really do not understand in this whole discussion is very s
Hi,
On 04 June 2012 17:24:31 Baptiste Daroussin wrote:
> On Sun, Jun 03, 2012 at 10:55:37PM +0200, O. Hartmann wrote:
> > On 06/03/12 15:29, Erich wrote:
> > >>
> > >> And if a port build is broken then the maintainer needs to fix it, that
> > >> is the solution.
> >
> > Look at the comment of t
On 06/04/12 17:24, Chris Rees wrote:
> On 3 June 2012 21:55, O. Hartmann wrote:
>> On 06/03/12 15:29, Erich wrote:
>>> Hi,
>>>
>>> On 03 June 2012 PM 5:14:10 Adam Strohl wrote:
On 6/3/2012 11:14, Erich wrote:
> What I really do not understand in this whole discussion is very simple.
Chris Nehren writes:
> The descriptions of the options assume the admin is familiar with the
> software they're installing. I do not think it is the FreeBSD Project's
> purview to document every option for every port. At the very least it'd
> take quite a lot of time and effort to document all of
On Mon, Jun 04, 2012 at 11:41:30 -0700 , Dave Hayes wrote:
> Yes there is...my point. :) Perhaps I was unclear. Optionsng is likely a
> fine project. However, it does not include the idea of extra
> documentation on the user selectable options provided to a port.
>
> Often when building a port I a
Chris Rees writes:
> On Jun 4, 2012 9:50 AM, "Dave Hayes" wrote:
>> Mark Linimon writes:
>> > On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote:
>> >> I see features and pkgng and things being offered up as solutions...
>> >> these are all well and good, but in my opinion more comprehen
On 04.06.12 18:04, xenophon\+freebsd wrote:
-Original Message-
From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
sta...@freebsd.org] On Behalf Of Daniel Kalchev
Sent: Saturday, June 02, 2012 12:42 AM
I really see no reason why your 'mail or calendaring server'
should be abl
On 3 June 2012 21:55, O. Hartmann wrote:
> On 06/03/12 15:29, Erich wrote:
>> Hi,
>>
>> On 03 June 2012 PM 5:14:10 Adam Strohl wrote:
>>> On 6/3/2012 11:14, Erich wrote:
What I really do not understand in this whole discussion is very simple.
Is it just a few people who run into problem
On Sun, Jun 03, 2012 at 10:55:37PM +0200, O. Hartmann wrote:
> On 06/03/12 15:29, Erich wrote:
> >>
> >> And if a port build is broken then the maintainer needs to fix it, that
> >> is the solution.
>
> Look at the comment of the maintainer of LibreOffice ...
LibreOffice is not a small port, I m
> -Original Message-
> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> sta...@freebsd.org] On Behalf Of Daniel Kalchev
> Sent: Saturday, June 02, 2012 12:42 AM
>
> I really see no reason why your 'mail or calendaring server'
> should be able to wipe your devices.. This is t
On Fri, Jun 01, 2012 at 05:03:26AM -0700, Mehmet Erol Sanliturk wrote:
> Dear All ,
>
> There is a thread
>
> "Why Are You Using FreeBSD ?"
>
>
Hello,
I'm using FreeBSD for most of my tasks and servers and i think it's great, but
this things could be improved:
- Good FUSE support. On
On 04.06.12 05:24, Dave Hayes wrote:
Anyway, given my workload, it will probably take me a man week to get
two virtualized test servers. Someone I know with a vmware gui and
windows is doing this in 15 minutes (and that's being careful). Just
my $0.02.
You are unfortunately comparing apple
On Jun 4, 2012 9:50 AM, "Dave Hayes" wrote:
>
> Mark Linimon writes:
> > On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote:
> >> I see features and pkgng and things being offered up as solutions...
> >> these are all well and good, but in my opinion more comprehensive
> >> documentation
On Mon, Jun 4, 2012 at 12:09 PM, Daniel Kalchev wrote:
> On 03.06.12 07:24, Erich wrote:
>> isn't this what I just suggested to be done by the team? Give the ports
>> tree a new version number and people can fall back to this then.
>>
>> Isn't this solution too simple to be done?
>
> As was mentio
On 03.06.12 07:24, Erich wrote:
isn't this what I just suggested to be done by the team? Give the ports tree a
new version number and people can fall back to this then.
Isn't this solution too simple to be done?
As was mentioned earlier in this discussion, by virtue of the ports tree
bein
Mark Linimon writes:
> On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote:
>> I see features and pkgng and things being offered up as solutions...
>> these are all well and good, but in my opinion more comprehensive
>> documentation and support in these areas would do more good than pkgng.
On 04/06/2012 00:30, Mark Andrews wrote:
> The ports system defaults are to use a common build/runtime tree
> but at the cost of a little more disk space each major application
> could have its own build/runtime tree. This is a tradeoff. Most
> of the time having a shared set of libraries is a wi
1 - 100 of 197 matches
Mail list logo
