On Wed, Mar 30, 2011 at 02:05:32PM +0800, Wilkinson, Alex wrote:
>
> 0n Wed, Mar 30, 2011 at 07:31:27AM +0200, Jo Galara wrote:
>
> >on Debian I'm using apticron which sends me an email if there are
> >updates available for installed packages. Is there a similar program for
> >Fr
On Sun, Jul 03, 2011 at 05:47:02PM +0200, Robert Millan wrote:
> isn't it enough if support is present in the FreeBSD
> version of these compilers (for production and development releases of
> FreeBSD), plus the latest release of the upstream version of each of
> those compilers?
You may find the
To me, it just makes things less readable.
mcl
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
On Mon, Sep 05, 2011 at 02:48:57PM -0500, Dan Nelson wrote:
> I suggest 2x RAM for systems less than 4gb or so. Anything more than 4GB of
> swap is probably never going to be used
I see you don't do mass package builds :-) Or, even build openoffice or some
of the math packages.
> and if it is u
(sorry to reply to Doug but not Dieter, but I have already deleted the
prior email)
> On 01/18/2012 16:58, Dieter BSD wrote:
> So you are saying that the Giant lock was completely removed in 7.0?
It was completely removed from the network stack. That was the missing
qualifier in his sentence.
S
On Tue, Jan 17, 2012 at 02:43:21AM +, Igor Mozolevsky wrote:
> To be realistic, I think any serious developer should expect to spend
> 70% of their development time on maintenance
s/developer/paid developer/ and you've got a correct model of how commercial
software companies work.
mcl
___
On Tue, Jan 17, 2012 at 06:45:17PM -0500, Daniel Eischen wrote:
> The problem I have with ports is that there is not a -stable branch
> that tracks with -stable core.
We've been working for 18 months to try to get the hardware infrastructure
in place to be able to consider such approaches.
> It d
On Thu, Jan 19, 2012 at 08:07:43AM +0100, vermaden wrote:
> I submit PRs and try to help test them as some developer/committer
> will pick up the PR, submit a patch to test, but it was MANY times
> that the response from developer/committer was way too long that
> I even DID NOT HAVE THE HARDWARE a
On Wed, Jan 18, 2012 at 02:18:50PM +0200, Andriy Gapon wrote:
> So software can already send the reminders, but the real problem is to
> assign the PRs in the first place. Currently most assignment are self-
> assignments.
My experience has been that assigning PRs to people who have not
specifica
On Sun, Jan 22, 2012 at 11:15:09PM +1000, Da Rock wrote:
> >Scroll up and count the serious and critical bugs too :)
> I didn't realise it broke the numbers into the sections.
Yeah. The problem is that, over time, the values in those fields has
become meaningless. Some of us try to triage what
> On 24 January 2012 18:36, Arnaud Lacombe wrote:
> It is less a problem of having the tools than having the will to do
> everything publicly. From experience, committers loves to do all kind
> of things privately/secretly.
Perhaps it's human nature because of all the increasingly nit-picky, pass
On Tue, Jan 24, 2012 at 12:24:22PM +0100, vermaden wrote:
> It would also be good to have some wiki.freebsd.org page that
> would describe what information is needed to fill a good PR
See:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ .
Your suggestion to include things
> I might just be also interested to review/comment code, discuss
> regressions, and architecture, for a change ;-)
> Unfortunately, such threads rarely ever happen. Most of the time, the
> only food provided is a really indigestible +5000/-3000 patch, where
> all the thinking, architectural design
On Wed, Jan 25, 2012 at 03:58:41AM -0500, Arnaud Lacombe wrote:
> > You seem to be obsessed by picking over
> > semantics and finding shortcomings to be aggreived over.
> >
> Semantics and proper, independent, API are crucial.
I'm talking about the semantics of the non-technical part: the wording
On Thu, Jan 26, 2012 at 10:23:43PM +, Mark Blackman wrote:
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-proc.html
>
> "New releases of FreeBSD are released from the -STABLE branch at
> approximately four month intervals."
That was our intention at one point. Obviously
On Thu, Jan 26, 2012 at 10:52:44PM +, Mark Blackman wrote:
> I suspect poor old RE is putting too much work into BETAs and RCs for
> point releases.
The counter-argument is that we have a lot more leeway to make mistakes
on a .0 release. We're not going to be cut any slack at all for shippin
On Thu, Jan 26, 2012 at 09:45:47PM +1000, Da Rock wrote:
> 1. Incidentally, what exactly does constitute a major release?
That point in time where we guarantee that we break a certain degree
of backwards compatibility. (Well, that's the key component. Feature-
additions ride on top of that.)
>
On Mon, Jun 11, 2012 at 03:38:56PM -0700, John Kozubik wrote:
> I am looking at the upcoming release schedule, and I only see 9.1
> listed - can anyone confirm or deny 8.4 ?
Although I am not on re@, AFAIK the only schedule that is on the table
is the one for 9.1.
mcl
On Wed, Jun 13, 2012 at 12:30:08AM +0400, Andrey Zonov wrote:
> No, I didn't. I want to fix the problem not just file a PR and wait
> for years.
I do understand your frustration, but we have some new people interested
in picking up and handling src-related PRs, so I see the situation as
improving
On Tue, Jun 12, 2012 at 07:08:08PM -0400, Jerry McAllister wrote:
> You sound like the people who can't decide to get something because a
> new version is going to come out sometime before they die.
That may be how it seems to end-users, but as we have heard multiple
times from people who use Free
On Wed, Jun 13, 2012 at 08:50:24AM -0700, Garrett Cooper wrote:
> The only way that this would really work is if there were dedicated
> sustaining engineers working on actively backporting code, testing it,
> committing it, etc.
I'm going to agree with Garrett here. IMHO we've reached (or surpass
On Thu, Jun 14, 2012 at 06:50:34AM +0200, Wojciech Puchar wrote:
> does it matter. cvsup RELENG_8 and you see updates are done constantly.
> just sometime somebody decide to change number :)
The difference is the freeze-and-test work that goes between "random
date" and "release time". This requir
On Thu, Jun 14, 2012 at 10:29:22AM +0200, Damien Fleuriot wrote:
> Whoever said STABLE is no good for production ?
>
> I used to make us stick to 8.2-RELEASE here at work, but some bugfixes
> are just too important to skip (we're running firewalls and had a
> problem with a CARP bug).
In theory w
On Fri, Jun 15, 2012 at 10:16:30AM +0200, Damien Fleuriot wrote:
> I'm thinking we might jump straight from 8.x to 10 when the time comes,
> I'm really looking forward to Gleb's work on CARP and PF ;)
I don't know why you might think one .0 release would be more mature
than another .0 release. Ma
On Tue, Jun 19, 2012 at 06:45:13PM -0400, Richard Yao wrote:
> That is already done in Gentoo FreeBSD, or do you want me to do the
> work for you to integrate OpenRC in the base system?
We want you to do the work to prove that it is an improvement. Otherwise
it's "just another claim."
You seem t
On Wed, Jun 20, 2012 at 04:17:52PM +0300, Vitaly Magerya wrote:
> The last time concurrent rc patches where proposed I measured boot time
> on my laptop (running 8.2-RELEASE i386 IIRC): out of 45 seconds from
> power on to login prompt, 20-25 where spent in rc, and parallel
> execution of it shaved
On Tue, Jul 17, 2012 at 01:56:33PM -0700, Dave Hayes wrote:
> I've been using FreeBSD since the 90s. My perception (over many
> years of observation) is that the FreeBSD people most able to
> document what exists and how to use it seem to also have the
> greatest resistance to writing any documenta
On Fri, Oct 26, 2012 at 09:34:20AM -0700, David O'Brien wrote:
> (there are no pre-build packages for 10-CURRENT).
Please see the first two entries on:
http://pkgbeta.freebsd.org/
mcl
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.
On Mon, May 28, 2007 at 12:15:28AM +0200, Michel Talon wrote:
> To gain some performance, a first idea would be to simplify
> bsd.ports.mk. I am convinced that a substantial part of the 4000 lines
> are historical crap which serve no useful purpose.
11272 of LOC in bsd.*.mk, but who's counting.
>
On Mon, Jun 18, 2007 at 02:35:59PM -0400, Mike Meyer wrote:
> While both FreeBSD and darwin ports (where I do development) have all
> the appropriate bits except oracle, the Linux distros don't have any
> of them in their packaging systems.
It might be nice to point that out to Oracle, as a way to
On Tue, Aug 14, 2007 at 03:49:50PM -0400, Dave Jones wrote:
> I'm unfamiliar with how patch submission works in FreeBSD,
> but hopefully someone can eyeball this for correctness
> and get it committed, or forward it on to the right people.
The way to make sure your patch doesn't just get lost in t
On Fri, Jan 11, 2008 at 09:12:27PM +0100, Ivan Voras wrote:
> These numbers seem strange and out of proportion. I know there has been
> prior cooperation with Coverity - is this just old data?
IIRC Coverity is not tracking our use of their software, at least in
those statistics. Someone was tell
On Fri, Jan 25, 2008 at 01:58:51PM +0800, william wong wrote:
> That brings me to another ponder: why juniper and cisco are using
> FreeBSD and not Linux even Linux performs better in an UP environment?
Other posters have mentioned that there is a mix of Linux and BSD at
Cisco. I don't work there
On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote:
> There is a better interpretation, which is that the only critical issue
> is lack of real users for this port, not lack of serial port support :).
My understanding is the the port is in a pre-alpha state due to unfinished
work in th
On Mon, Feb 02, 2009 at 05:17:38PM +0100, Dominic Fandrey wrote:
> I want to request a responsibility timeout for bin/120784
(with bugmeister hat) AFAIK no one else other than rodrigc has been
doing work on the mount utilities, so I don't know who else to assign
it to.
mcl
___
On Tue, Feb 24, 2009 at 10:24:29PM -0500, Chuck Robey wrote:
> Why is that? Is XFree86 not getting any fixes?
We didn't have anyone that wanted to support it after we switched the
default to xorg. (We actually need more people willing to support xorg,
as well).
mcl
_
On Fri, May 15, 2009 at 06:54:53PM +0200, Julian Stacey wrote:
>- Those that pushed to censor jobs@ some years ago (& succesors?)
> are not worth having, j...@freebsd would be better without them.
In your opinion. Not in mine.
>- Where better than hackers@ to look for support to lib
On Wed, Sep 23, 2009 at 05:54:34PM +0200, Julian H. Stacey wrote:
> 4.11 fell out of security support some while back, but
> http://www.freebsd.org/security/index.html
> only lists what's still in, not what fell out when.
Then see http://people.freebsd.org/~linimon/schedule/milestones.html.
On Thu, Sep 24, 2009 at 01:35:21PM -0300, Leandro Quibem Magnabosco wrote:
> I think that one questions pops into the minds of a lot of people right
> now: Why not just use DragonFly BSD?
Feel free, but take it off-list, please.
mcl
___
freebsd-hacker
[adding freebsd-bugbusters@ to the Cc:]
I'm sorry I didn't respond to your earlier message. I am currently way
behind on tasks that I've already promised people.
The KDE howto that you cited
(http://quality.kde.org/develop/howto/howtobugs.php)
is quite a good one. Our pr-guidelines document is
On Thu, Feb 04, 2010 at 04:09:48AM -0600, Mark Linimon wrote:
> Reports that are duplicates indicate that various users are being affected
> by one underlying problem. At one point I was trying to gather them all
> into a page. I was hoping more people would do the analysis an
fwiw, the canonical way to find out if a port will package up in a
clean environment (choort, with dependencies all loaded via package)
is on http://pointyhat.freebsd.org/errorlogs/ , e.g.,
http://pointyhat.freebsd.org/errorlogs/i386-8-full/ .
http://portsmon.freebsd.org gives you lots of cross-re
On Sun, Mar 14, 2010 at 01:12:14PM +0100, Alexander Best wrote:
> ah ok. thanks for the hint. just wanted to spare linimon from dealing with
> such minor prs. ;)
It's much more efficient for the project to have them in GNATS.
I tend to triage PRs with the TV on, so it's not like the trivial ones
When I initially wrote the Ports Status report I included information
about a project that Edwin Groothuis created. At that time I neglected
to get his approval for that text, and that was an oversight and a
mistake on my part and I apologize. I did not intend for anyone to get
the impression tha
Synopsis: Disk IO Causes multimedia/mplayer To Drop Frames
Responsible-Changed-From-To: freebsd-hackers->freebsd-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 10 02:24:33 UTC 2006
Responsible-Changed-Why:
Fix up Category and Responsible.
http://www.freebsd.org/cgi/query-
On Wed, 1 Dec 2004, Scott Long wrote:
> 2. New installer. [... sysinstall] is fairly good at the simple
> task that it does [ ... ]
I'll put my bugmeister-hat on and simply say that query-pr suggests
otherwise. I have not spent sufficient time examining each of the
PRs to figure out what the b
> The only thing any of the committers cares about is what they think.
> Got a problem? Submit a patch. Don't like the way things are done?
> Submit a patch. Don't like how such-and-such a util works? Submit a
> patch.
Please suggest an alternative, given that almost all the labor
is volunteer lab
> I forgot to mention on rather important factor in this equation:
Er, this is the *only* important factor. IMHO, it made most of the
previous conversation be completely off-the-rails.
> If nothing happens, vinum is going to break even more very soon.
No ... if you do a commit that changes the
> If vinum means a lot to you, you should do something to get it above
> that threshold: start debugging/coding, learn to code if need be,
> donate money so somebody else can code if you can't do anything
> else.
I don't use vinum so I have no stake in this.
OTOH I'm not announcing changes which
49 matches
Mail list logo
