Re: bin/139146 still not right in FreeBSD 8.2 (-m32 on amd64)?

On Wed, Mar 09, 2011 at 03:15:39PM -0500, Thomas David Rivers wrote: > But, when I try to build 32-bit programs I get problems linking, > and I stumbled onto PR bin/139146. That one was closed as a duplicate of gnu/112215. I've forwarded your email to GNATS with the followup redirected there. mc

Re: SCHED_ULE should not be the default

I'm not on the Release Engineering Team, and in fact don't have a src commit bit ... but this close to a major release, no, it's too late to change the default. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fre

status of ports and clang

I have recently been able to get the new build cluster on pointyhat-west set up to run full builds of ports with clang on amd64-9. I have documented the latest results on the wiki: http://wiki.freebsd.org/PortsAndClang If you are interested in working on ports being built via clang, this is yo

Re: Odd reboot problems with 9.0-RELEASE i386

On Fri, Jan 20, 2012 at 07:23:35PM +0200, Andriy Gapon wrote: > I think that it probably could be easier for you and for those reviewing your > kernel config if you 'include'-d GENERIC into your kernel config and then used > device/nodevice, options/nooptions, etc to make your customizations. I st

Re: FreeBSD9 and the sheer number of problem reports

On Sun, Feb 26, 2012 at 06:32:17PM +0700, Erich Dollansky wrote: > > There's no such odd/even number policy with FreeBSD-- I think you're > > thinking of another OS ;) > > > maybe something got stuck in my head with the move from 4 to 5. Yes, 5 was the Great Leap where true SMP was introduced. I

Re: FreeBSD9 and the sheer number of problem reports

On Sun, Feb 26, 2012 at 09:27:58AM -0300, H wrote: > it is release engineering who could establish a little bit more time > between code-freeze and RELEASE As you will see from the (very) long discussion that you are about to read, there has to be a compromise. As it was, the release process was

Re: ports usable or not [was: flowtable usable or not]

On Fri, Mar 02, 2012 at 03:35:24PM +0100, Nomen Nescio wrote: > If you use [!i386] you are likely to find problems with ports and > this gets amplified if you use nonstandard (read stuff not everybody uses) > ports. Fair enough. > I have found several ports broken for many releases in a row. The

Re: ports usable or not [was: flowtable usable or not]

Yeah, I've been trying to prioritize some -exps that are blocking other people right now. I know there's many more :-) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail

Re: flowtable usable or not

On Sat, Mar 03, 2012 at 03:44:42AM -0300, H wrote: > nobody want to read, they want a desktop nothing else, something silly > and easy to read email and write docs and surf on the net, listen to a > CD, they need to put a cd into the drive, running install process, > reboot, using, nothing else and

Re: ports usable or not [was: flowtable usable or not]

On Sat, Mar 03, 2012 at 09:08:28PM +0100, Nomen Nescio wrote: > Thanks mcl. I am off on other things for now but I will file PRs next time > I come across something. In the past I have emailed the port maintainer and > the answer is usually "yeah I know". After a few of those I thought filing > PRs

Re: Request for flowtable testers and actionable feedback RE: flowtable usable or not

On Mon, Mar 05, 2012 at 02:28:37AM -0300, H wrote: > because you don't care about what really matters, people, users, you > do not even know how to talk to them I've been criticized for saying this to a user before, but I'm going to repeat it here regardless of consequences. I'm sorry, you (as a

Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation

On Tue, May 15, 2012 at 08:12:05PM -0500, Larry Rosenman wrote: > Would it be possible for the next 9.x release to set hw.memtest.tests="0" > when we discover we're under a hypervisor to avoid doing the tests? (or > default it to 0 in the installer kernel?)? Actually, that's already been fixed, an

Re: Why Are You NOT Using FreeBSD ?

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 there is one very

Re: Why Are You NOT Using FreeBSD ?

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

Re: Implications of pkgng, was Re: Why Are You NOT Using FreeBSD ?

On Sun, Jun 03, 2012 at 09:31:19PM +0200, Mel Flynn wrote: > Once the base system supports binary upgrades of packages through pkgng > it should solve a lot of issues that people have with production systems > now IMHO, s/solve/expose/ :-) It will then be up to use to solve them. mcl ___

Re: Why Are You NOT Using FreeBSD ?

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. IMHO pkgng and optionsng

Re: Why Are You NOT Using FreeBSD?

On Mon, Jun 04, 2012 at 07:49:02AM +0700, Erich wrote: > can you still install the ports tree and its applications on a FreeBSD 4.4? No. When 4.11 finally went EOL on 01/31/2007 we removed all the compatiblity code, because by that time supporting both was increasing the maintenance burden on our

Re: Why Are You NOT Using FreeBSD?

> 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

Re: Why Are You NOT Using FreeBSD?

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

Re: Why Are You NOT Using FreeBSD?

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

Re: Why Are You NOT Using FreeBSD?

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,

Re: ports

On Fri, May 28, 2010 at 02:16:31PM +0300, Gregory Edigarov wrote: > Which is the minimal current version of system supported by ports? We are currently supporting the same systems that secteam does, so, for each branch, 6.4, 7.1, and 8.0, respectively. The secteam matrix can be found at http://ww

Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon

> > The reason is performance for overall network stack, not ideology. > For a practical reasons, "it works but slow" is better than > "doesn't work at all (due to absence of code in the src tree)". > "Make it work. Make it right. Make it fast. In that order", know this? > Sacrificing "work" for "

Re: Can't build boot blocks after new GPT attributes added

On Wed, Oct 27, 2010 at 09:27:03AM -0400, John Baldwin wrote: > Maybe you could add text to the handbook to say this, but it is already > implicitly assumed in the handbook section you are referring to since it > assumes you can safely compile a new kernel, etc. [...] If we were to > document t

Re: Support for Areca ARC-1300-4X on 8-STABLE?

On Wed, Nov 24, 2010 at 10:01:31AM -0500, Paul Mather wrote: > I'd also hope that such a vendor would be contributing its drivers > directly into the source tree rather than having a separate set of > patches or downloads for end-users to fiddle about with. In a perfect world, yes, but not all ven

Re: sun4v arch

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

Re: Fwd: FreeBSD 7.1 Content

On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: > Additionally, I've never seen a clear way of synchronizing a > local ports tree to that used to create the "LATEST" packages. There's really not a way to easily track this, especially with the fact that we tend to run incremental updat

Re: Fwd: FreeBSD 7.1 Content

On Mon, Sep 08, 2008 at 10:27:31PM -0400, Randy Pratt wrote: > Personally, I quit using packages in the 2.x-3.x days since there were > far less problems building everything from sources and not trying to > mix pre-built packages and locally built ports. We are doing much better these days in term

Re: Upcoming Releases Schedule...

On Tue, Sep 16, 2008 at 04:30:26PM +1000, Andrew Snow wrote: > I think FreeBSD is getting in a difficult position now because there's > so much cool new stuff being shoe-horned in, but without the necessary > volume of contributors to back it up with testing and bug fixes. We're interested in su

(no subject)

On Wed, Sep 24, 2008 at 09:32:52AM +1000, jonathan michaels wrote: > thank you gentle peoples for working out this solution. Unfortunately it has not been 'worked out' with the decision-makers. It has been suggested. Doing s/suggested/agreed to/ is not an automatic process. mcl _

Re: visibility of release process

On Mon, Dec 08, 2008 at 08:57:37PM +1100, Aristedes Maniatis wrote: > 3. Improvements to the bug tracker. Personally I'd love to see > something like Jira used [4] with all the sophistication of workflow, > release notes, voting for bugs, etc, etc. I have some notes for some prototyping ideas,

Re: Big problems with 7.1 locking up :-(

On Mon, Jan 19, 2009 at 04:59:59PM -0500, Pete Carah wrote: > I shouldn't *have* to kernel debug for a normal usage of an > official release. Agreed, but the problems that people are having do not seem to have arisen on any of the systems that ran prelease tests for 7.1. Although I'm sure it does

reminder: bugathon upcoming this weekend

Starting this Friday, we are going to hold a bugathon to work through some of the network-related PRs. More details, and a list of resources, are available at http://wiki.freebsd.org/Bugathons/January2009. I have come up with a page that details a subset of those PRs as a set of suggested PRs: h

Re: NSIS compile failed on FreeBSD 7.2

On Fri, Nov 20, 2009 at 11:46:13AM -0800, Jeremy Chadwick wrote: > If that's indeed the case, then the port Makefile needs to be modified > to reject building on any architectures other than i386. This should > suffice: > > ONLY_FOR_ARCHS= i386 There's a (fine?) distinction between the usa

Re: ACPI Error: A valid RSDP was not found 20090521 tbxfroot-309

On Thu, Dec 10, 2009 at 08:48:31AM -0500, John Baldwin wrote: > Hmmm, there isn't anything CPU-specific in ULE vs 4BSD, and I would expect > ULE to work fine on a PIII. I would generally expect device timeouts to be > more of a driver issue than a scheduler issue. We've run nodes in the package b

Re: Using RELENG_8 to compile for older RELENG_x

On Wed, Dec 16, 2009 at 11:28:51AM +0100, Roland Smith wrote: > the current ports tree isn't guaranteed to work on [4.x] either. s/isn't guaranteed to/is guaranteed not to/ (sorry) You might want to experiment with checking out a ports tree as of tag RELEASE_4_EOL and trying to pull in newer pie

Re: Using RELENG_8 to compile for older RELENG_x

On Wed, Dec 16, 2009 at 12:54:52PM +0100, Roland Smith wrote: > In the days before 5.3 or even 6.0 I could understand why people clung to > 4.x. But now it seems like inviting trouble. 5.3 still had a lot of sharp edges (a lot of things were merged into it just prior to release). But at this poin

Re: Are there schedules for 7.3-RELEASE?

On Thu, Jan 07, 2010 at 12:11:30AM +0100, Miroslav Lachman wrote: > Are there (when will be) plans for 7.3-RELEASE as was for 7.2 on this > page: http://www.freebsd.org/releases/7.2R/schedule.html ? Dates are currently under discussion. mcl ___ freebs

Re: posting coding bounties, appropriate money amounts?

On Fri, Jan 22, 2010 at 07:20:18PM -0600, Adam Vande More wrote: > > I'd be willing to put up a thousand USD or possibly more depending on > > what sort of work was being considered. I suppose a better choice would > > be for someone here to make a list of issues which the community feels > > need

Re: Complete ports thaw

It probably bears repeating that the tree will be unstable for the next few days while a number of large commits hit the tree. These were held off during the release process to make life easier in case portmgr had to do tag-slips. Image processing libraries, xorg, kde, and gnome are scheduled to

Re: Can't boot after make installworld

On Mon, Mar 22, 2010 at 08:41:35PM +, Krzysztof Dajka wrote: > But still I am confused with FreeBSD naming and it's relation with > tags which are used in standard-supfile. Please see the following for an overview: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT

Re: FreeBSD Release 8.0 floppy images

You can still build them. They just won't be built by default. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

upcoming bugathon this weekend

If you're interested in helping out on our PR database problems, please see my posting on freebsd-bugbusters@: We're having a bugathon this weekend, with the agenda being mostly to figure out where we are, who would like to help, and c

Re: /usr/bin/objformat is missing

On Mon, Jan 28, 2008 at 04:55:01PM -0800, Jeremy Chadwick wrote: > I don't agree with any port creating a file in /usr/bin, and it's safe > to say others will not agree with it either. In particular, portmgr will mark such a port as BROKEN :-) mcl ___ f

fwd: [EMAIL PROTECTED]: results of the 20080125 bugathon]

Here's a repost of the message I just sent to [EMAIL PROTECTED] Followups there, please. Thanks. mcl - Forwarded message from Mark Linimon <[EMAIL PROTECTED]> - Over 30 people participated in this bugathon. Thanks to all who participated! During the 3 days, we closed aro

Re: 7.0-RC2 package glitch

On Sat, Feb 16, 2008 at 03:13:35PM -0800, Wayne Chapeskie wrote: > The RC2 sysinstall misses six packages, which are included on disc 1, > which RC1 did install: > >imake-1.0.2_4,1 >makedepend-1.0.1,1 >gccmakedep-1.0.2 >xorg-cf-files-1.0.2_2 >xorg-nestserver-1.4,1 >

Re: make KNOBS

On Mon, Feb 25, 2008 at 09:55:22PM -0800, Chris H. wrote: > Is there, or does anyone maintain a KNOBS list possibly categorized > by application/port/version, etc...? ports/KNOBS? mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/

Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE

On Thu, Feb 28, 2008 at 02:47:28PM +, Chris wrote: > Did they push ahead with release because waiting for the mia dev? There's a lot of things that go into deciding when to release. The release cycle this time was not supposed to be as long as it was. We kept finding showstoppers and needing

Re: challenge: end of life for 6.2 is premature with buggy 6.3

kris points out that I botched my reply by confusing contributions from 2 different posters. My apologies (I have not closely tracked the entire thread). Nevertheless, the URLs and the summary information should still be of interest. mcl ___ freebsd-st

Re: challenge: end of life for 6.2 is premature with buggy 6.3

On Thu, Jun 05, 2008 at 05:39:36PM +0200, Kris Kennaway wrote: > You seem awful hostile - do you really think that's the best way to > represent the project you're involved with? When confronted with "what you are doing is wrong, but I am not going to tell you what it is because if you cared you'

new wiki page to collect information about the ATA subsystem

Jeremy Chadwick (koitsu@) has been gathering together information on the wiki about commonly seen problems with FreeBSD: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting Based on a discussion on #freebsd-bugb

Re: Who is responsible for Heimdal/Kerberos in FreeBSD

On Fri, Aug 03, 2012 at 12:51:17PM +0100, Attila Bogár wrote: > On 02/08/12 16:04, Chris Nehren wrote: > >Rather than sending repeated mails to the list (which you've > >already seen get dropped on the floor), consider using the proper > >channels for reporting bugs. Send a PR. See > >http://www.fr

Re: Clang as default compiler

On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote: > Is there a specif PR to use for ports that fails with clang and does > not specify to use gcc ( > devel/cdecl and deskutils/calibre so were > the culprits so far) There is no specific PR. We have not yet placed the requirement on

Re: Clang as default compiler

On Wed, Sep 12, 2012 at 08:00:46AM +0100, Chris Rees wrote: > We don't want thousands of PRs duplicating the information from a simple > list of failures. Thanks, that was the point I was trying to make. mcl ___ freebsd-stable@freebsd.org mailing list h

Re: Clang as default compiler

On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote: > How about run automated test on two poudriere setups, one with CLANG set > up, other with USE_GCC=4.2 applied to all ports which marked as broken, We have been running various tests for quite some time. > Is there somewhere lis

Re: FreeBSD 10-CURRENT and 9-STABLE snapshots

On Wed, Oct 10, 2012 at 07:04:22PM +0200, Claude Buisson wrote: > As an addon, according to lists.freebsd.org, svn-ports have not been > updated since more than a day... This is an unrelated problem, caused by machine upgrades/moves at our main data center. > - the recently created snapshots.glen

Re: Will we get a RELEASE-9.1 for Christmas?

On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: > the ISO are on the master server The release is official when, and only when, a signed email from the release engineering team says that it is. In a past release cycle there was indeed a last-minute fix that had to be made after the ISO

Re: FreeBSD 9.1-RELEASE crashes almost daily; backtraces always list zfs routines

dumps somewhere and include a URL to them in a followup to the PR. Thanks. Mark Linimon, on behalf of bugmeister ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "fre

Re: 9.1 minimal ram requirements

On Wed, Dec 26, 2012 at 06:02:33PM +0100, Zoran Kolic wrote: > > Seeing 9.1-RELEASE instead 9.1-PRERELASE > > or 9.1-RC4 is also a bad suprise for me... > > I assume it does not look like release is the lack > of packages. What you are seeing is behind-the-scenes preparation. The release is offi

Re: 9.1 minimal ram requirements

In an ideal world, the bits that will almost certainly become FreeBSD 9.1 would not appear on the masters, or any of the mirrors, until the same instant that the release announcement is set to freebsd-annou...@freebsd.org. In practice this doesn't happen. If there is some clever way for that to h

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

On Thu, Jan 17, 2013 at 09:15:02AM -0600, Brooks Davis wrote: > Not unless you consider adding new functions in a reserved namespace > (str*) to be ABI breakage. Well, what often happens is that when we add new functions, ports break. I think deciding whether this is or is not "ABI breakage" is se

Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: > I'm not sure why I'm being jumped on in this weeks old report of a > now-fixed problem. I'm sorry, I'm that far behind in email. I did not realize the problem had already been solved. More often than not the problem is simply "throw

Re: CLANG and -fstack-protector

On Thu, Feb 07, 2013 at 11:52:42PM +0100, Jeremie Le Hen wrote: > You can do this, it will work for most of the ports but some ports do > not honor CFLAGS. Ports that don't honor CFLAGS are broken ports. Having said that, the last time I ran a script that looked for them (and other things like CX

Re: New FreeBSD snapshots available: stable/10 (20150625 r284813)

On Wed, Jul 01, 2015 at 11:34:17AM -0400, Kurt Lidl wrote: > Of course, with no network connection, it's not a very useful machine, There are PCI slots on mine :-) ok, joking aside, this is indeed not useful. But it's useful to note that a couple of months ago, I was running my v245 hard, and it

Re: 10.2-Beta i386..what's wrong..?

On Fri, Jul 24, 2015 at 02:19:20AM +0200, Michelle Sullivan wrote: > Why is zfs on i386 so hard? zfs is a resource hog. i386 is not able to handle the demand as well as amd64. I have never, ever, heard of anyone who has a deep understanding of zfs on FreeBSD recommend anything other than amd64.

Re: 10.2-Beta i386..what's wrong..?

On Fri, Jul 24, 2015 at 12:43:43AM +, Glen Barber wrote: > Even on amd64, you need to tune the system with less than 4GB RAM. The only correct answer to "how much RAM do you need to run ZFS" is "always more" AFAICT. mcl ___ freebsd-stable@freebsd.or

Re: FCP-0101: Deprecating most 10/100 Ethernet drivers

On Wed, Oct 24, 2018 at 05:19:33AM -0700, Rodney W. Grimes wrote: > And I have read case law that boiled down to the presents vs absence > of a comma If we are now going to evaluate all proposed changes to FreeBSD on the same rigid principles as the US legal system, I'm done. mcl

Re: What will be tier 1 for 12.0-Release?

> > Good to see that there are pkg builds for powerpc64 these > > days: FreeBSD:12:powerpc64 and FreeBSD:11:powerpc64 are > > listed in the Tier-2 support package sets list as well. uh ... those were probably the last ones I did. AFAIK no package building has been done at isc for years. mcl ___

Re: What will be tier 1 for 12.0-Release?

On Wed, Oct 24, 2018 at 04:39:41PM +, Mark Linimon wrote: > uh ... those were probably the last ones I did. never mind, this is a new machine under test. I missed seeing the listing even when I looked at pkg.FreeBSD.org ... earlier today.

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

On Sun, Dec 16, 2018 at 06:12:35PM -0700, Alan Somers wrote: > As for powerpc on tier 1, I'm afraid that it's not likely to ever > happen. Powerpc is dying. If anybody were buying new ppc hardware, > then it would be a different story. But I predict that powerpc is > likely to be dropped than to

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote: > I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) > on my eMac. I don't know of anyone else who has tried to run it. The server-class ports on powerpc64 have been in good shape for several years. However, the desk

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

If we are talking powerpc32 and not powerpc64 (as I assumed), the one developer continuing to actively work on it is jhibbits@. Perhaps he can give you a status report. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/li

Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

On Sun, Dec 16, 2018 at 08:21:14PM -0600, Justin Hibbits wrote: > You can try to build the broken ports either by deleting the BROKEN > line in the Makefile True, but see below ... > or through some poudriere trickery -T Try building BROKEN ports by defining TRYBROKEN for the build. (Thi

Re: php56

AFAIK you can either: - use packages and revert to 2018Q4; or - re-add the sources locally and compile them from source. IIUC those are your only two options. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/

Re: DNS Flag Day and freebsd.org problems

I have already forwarded the email to clusteradm@. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: release cycle

On Sat, Jun 02, 2007 at 08:45:26AM +0100, Chris wrote: > Given that Kris repeatedly tells me and others that the ports system > is only supported on the latest freebsd release (meaning one has to be > upgrading freebsd on their servers every few months to get this > support) if 7.0 and 6.3 are rele

Re: upgrade 6.2 to xorg 7.2

On Fri, Jun 08, 2007 at 03:26:21PM -0400, Stephen Clark wrote: > Thats another question - why aren't packages released simultaneously > with the ports update? There's a circular dependency here. The ports tree is updated by checkins, which is then pushed to the package building system, which the

Re: upgrade 6.2 to xorg 7.2

On Fri, Jun 08, 2007 at 04:20:29PM -0400, Stephen Clark wrote: > So I should wait a about week after I do a cvsup of ports - then > hopefully most of the packages will be there - right? Yes, but you'll have to check. Some ports (not the X11 ones) can't be packaged due to licensing restrictions.

Re: rc.local equivalent

On Thu, Jul 12, 2007 at 01:47:53PM -0700, Doug Barton wrote: > There is a big difference between the current status, "rc.local is > still supported, however you will probably get better results using > local rc.d scripts;" and "This is going away, so stop using it." The text from rc(8): The rc.

Re: removing external usb hdd without unmounting causes reboot?

On Wed, Jul 18, 2007 at 11:42:26AM +0200, Momchil Ivanov wrote: > accidently unplugged the USB hub to which my external hdd together with a > mouse were connected and this caused my machine to freeze for some seconds > and then reboot. Yes, this is a known problem, for which there is no workarou

Re: removing external usb hdd without unmounting causes reboot?

On Wed, Jul 18, 2007 at 10:05:59AM -0700, Jeremy Chadwick wrote: > Bottom line here is that the kernel panics when removing a USB device > that has filesystems mounted. s/USB // > I also have a hard time believing that the reason it hasn't been fixed > is because "there isn't an easy fix". I'm u

Re: Progress with usability of AMD64

[note: this question probably should have been asked and answered on freebsd-ports@, but I'll go ahead and answer it here in any case.] The latest chart that compares package status across build environments is at http://portsmon.freebsd.org/chartsandgraphs/package_comparison.html. Note: the detai

[HEADSUP] preparations for ports release for 7.0

This is a pointer to the headsup I posted to freebsd-ports@ detailing the switch of portsmon's default build environment from i386-6 to i386-7. This controls such things as determination of whether a port is marked "broken" (e.g. with gcc4.2.) The first set of email reminders based on this have al

Re: Is it O.K. to use the 7.0 ports tree on 6.3 ?

On Friday 23 November 2007, Pete French wrote: > is it safe to simply untar the ports.tgz file from 7.0 on the 6.3 > machines, rename INDEX-7 to INDEX-6 and install away, or are there > more subtle differences to tran the unwary ? The dependencies can vary depending on OS release, so it's not guar

Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD

On Sun, Dec 02, 2007 at 12:37:32AM +0300, Alexey Vlasov wrote: > I decided to install FreeBSD 6.2 i386 on one of the servers, and the > result was totally non productive. The 6.x series was intended to get us back to the stability that we had had pre-SMP integration. I believe we mostly succeeded

Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD

On Sunday 02 December 2007, Alexey Vlasov wrote: > I used 7.0-BETA3 and it is much worse. Ouch. A lot of systems see improvement. Thanks for trying it out. I hope that one of the people that has been doing the actual work can now comment (I am just an onlooker), and that you can be patient in t

PR backlog [was: Re: usb/umass, devfs: this sucks]

On Wed, Dec 26, 2007 at 06:15:16PM +0100, Henrik Gulbrandsen wrote: > Fixing and merging are good, but it seems to me (as an occasional patch > contributor without commit privileges) that the bottleneck for USB is > still in the handling of incoming patches [...] if a one-line fix > such as that in

Re: PR backlog

On Wed, Dec 26, 2007 at 12:43:06PM -0800, Richard Neese wrote: > Point and Fax I have emaile Sobomax about fixing and updating the asterisk > ports. and have sent patches but never got a reply in 9 months. For situations like this you need to email [EMAIL PROTECTED] We already have defined para

Re: PR backlog [was: Re: usb/umass, devfs: this sucks]

On Sun, Dec 30, 2007 at 01:01:19AM +0100, Alexander Leidinger wrote: > Quoting Mark Linimon <[EMAIL PROTECTED]> (from Wed, 26 Dec 2007 > 12:04:15 -0600): > > > - The creation of a weekly posting "bugs the bugmeister team thinks are > > ready for commit".

HEADSUP: new wiki page: State of Packages on Sparc64

I've just posted a message with that title to sparc64@ with crosspost to [EMAIL PROTECTED] If you're interested in deciding on where we're going with sparc64, I invite you to join that thread. (Please don't reply to this message; 2 lists is probably one too many). mcl ___

Re: 6.3-RELEASE

On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote: > So may I guess that we have a release ? This question happens every time we get near a release. There will be a release when, and only when, a signed email is sent from the Release Engineering team to the various mailing lists.

Re: 6.3-RELEASE

On Thu, Jan 17, 2008 at 01:59:01PM -0800, Josef Grosch wrote: > I have a mirror at work (Juniper Networks) and we have had all the > bits since Tuesday. You can't have; the final sparc64-6 packages were just finished yesterday, at the last second. mcl _

Re: FreeBSD 6.3-RELEASE Available

On Fri, Jan 18, 2008 at 03:51:43PM -0500, Ken Smith wrote: > Due to resource limitations (both human and computer) there won't > be an ia64 6.3-RELEASE but there will be an ia64 7.0-RELEASE. Unless something changes rapidly, ia64-7 will not have any packages shipped with it: the last I tried, it w

Re: FreeBSD 7.2 Release process starting...

On Sun, Mar 22, 2009 at 09:18:03AM +1100, Aristedes Maniatis wrote: > Is there any way to automatically create such a page from the bug > tracker? Not that fills in the dates, no. We are working on a prototype to track particular PRs. mcl ___ freebsd

Re: sshpass

Please submit this via bugzilla so that it will not get lost in all the mailing list traffic. Thank you. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-

Re: Where is 10.2-STABLE?

On Thu, Mar 31, 2016 at 10:32:45AM +1100, Jason Tubnor wrote: > 10.3-RELEASE has been available for a few days now No, it hasn't. The bits for what _may be_ 10.3-RELEASE, barring the finding of any last-minute problems, are what is there. In at least one previous release cycle, last-minute probl

Re: Where is 10.2-STABLE?

On Wed, Mar 30, 2016 at 11:04:30PM -0700, Ronald F. Guilmette wrote: > I would however like to ask if there is an ETA for 10.3-RELEASE > actually being official and final. >From the front page of www.freebsd.org, click on the link "Upcoming: 10.3" which will take you to https://www.freebsd.org/rel

Re: Benchmarks results for FreeBSD 11

On Mon, Aug 22, 2016 at 09:57:24AM +1000, Dewayne Geraghty wrote: > unless knowledgable people respond publicly and/or in the phoronix > forums [...] this interpretation of reality will be fixed in decision- > makers' minds and consequently the uptake (and support) of FreeBSD. IIRC this has been d

Re: Benchmarks results for Compilers on FreeBSD 11

I'll demur just a bit on your points. On Mon, Aug 29, 2016 at 08:51:02PM -0700, K. Macy wrote: > "we need a compiler to build the system" (a prebuilt package does that > just fine), Well, yes, for a tier-1 machine; and one that is connected to the network. > I can't speak for the whole universe

Re: Nightly disk-related panic since upgrade to 10.3

On Fri, Oct 21, 2016 at 10:14:26AM +0200, Andrea Venturoli wrote: > I've tried this way, but altough I'm quite proficient with [k]gdb I tend to > get lost in FreeBSD's kernel's source code, which, unfortunately, I'm not > familiar with. > > BTW, I had read that book years ago; I searched for it no

  1   2   >