Re: Issue probably with `top` and Uncompressed ARC display
On Sun, 26 Aug 2018 at 04:47, Dmitriy M. wrote: > > Hi all, > > Got issue with displaying Uncompressed ARC in `top` (K Uncompressed and > negative Ratio) : ... I don't want to be the person that just asks you to test on HEAD but in this case, top(1) has been extensively modified in head/-current. You should be able to test by just doing this svn co svn://svn.freebsd.org/base/head/usr.bin/top cd top make $(make -V.OBJDIR)/top If its still an issue I'll look deeper. -- Eitan Adler ___ 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: mail coredumping on yesterdays STABLE
On Fri, 6 Jul 2018 at 07:28, Eitan Adler wrote: > > On Fri, 6 Jul 2018 at 07:06, Pete French wrote: > > > > > Understood. Like I said, my development box is dead, so expect nothing > > > for the next couple of weeks [0] unless someone gets to it first. > > > > Ok, no worries. Will you revert the chnage in STABLE until then, or > > should I continue running with it reverted locally ? I will try and > > look at it myself if I get a moment. > > I don't have the capability to commit right now. Mark Johnston fixed this. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230196 -- Eitan Adler ___ 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: mail coredumping on yesterdays STABLE
On Fri, 6 Jul 2018 at 07:06, Pete French wrote: > > > Understood. Like I said, my development box is dead, so expect nothing > > for the next couple of weeks [0] unless someone gets to it first. > > Ok, no worries. Will you revert the chnage in STABLE until then, or > should I continue running with it reverted locally ? I will try and > look at it myself if I get a moment. I don't have the capability to commit right now. -- Eitan Adler ___ 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: mail coredumping on yesterdays STABLE
On Fri, 6 Jul 2018 at 06:45, Pete French wrote: > > > Am going to try that. I should have added that the cordeump happens when > > I am viewing an email inside 'more' and I quit out of it, not when I try > > and delete it, I was wrong about that. > > > > Will give it a go with that chnage revertsed and let you know > > Reverting the chnage makes the coredump go away, so am back to > using command line mail again. Appologies for the top-positing > of the pervious post! Understood. Like I said, my development box is dead, so expect nothing for the next couple of weeks [0] unless someone gets to it first. [0] even once it gets fixed, I have to catch up on several projects. -- Eitan Adler ___ 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: mail coredumping on yesterdays STABLE
On Fri, 6 Jul 2018 at 05:52, Pete French wrote: > > /usr/bin.mail (still my preferred mail reader) has just started > coredumping on me when I delete seom messages. A trace is below, > and I notice http://www.freshbsd.org/commit/freebsd/r335693 > is applying some fixes in the area I am seeing coredumps If you revert the change does it succeed? My development machine is completely dead right now, but it is possible I missed a commit or otherwise made an error. -- Eitan Adler ___ 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: jail related inconsistencies in FreeBSD tools parameters
On 23 June 2018 at 08:50, James Gritton wrote: > On 2018-06-23 09:45, Eitan Adler wrote: >> >> On 23 June 2018 at 08:30, James Gritton wrote: >>> >>> On 2018-06-22 16:03, Miroslav Lachman wrote: >>>> >>>> >>>> Chris H wrote on 2018/06/22 23:46: >>>>> >>>>> >>>>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >>>>> <000.f...@quip.cz> >>>>> said >>>>> >>>>>> I don't know if it is better to discuss it in jail@ or stable@ list so >>>>>> a >>>>>> do cross-post. >>>>>> >>>>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>>>> taking JID as parameter. >>>>>> >>>>>> For example "sockstat" takes -j JID "Show only sockets belonging to >>>>>> the >>>>>> specified jail ID" and it means numeric ID only. >>>>>> On the other hand "ps" takes -J JID "This may be either the jid or >>>>>> name >>>>>> of the jail. Use -J 0 to display only host processes." >>>>>> The same apply for "top", it understands jid as a number or name of >>>>>> the >>>>>> jail too. >>>>>> Then again "cpuset" takes only numerical ID of the jail... >>>>>> >>>>>> Shouldn't it be consistent across all FreeBSD base utilities so all of >>>>>> them can use numerical ID and name? >>>>> >>>>> >>>>> Good idea! Are you offering to create a patch? ;-) >>>>> It'd be my guess that given they weren't all created at the same time, >>>>> nor >>>>> the same individual; that (quite probably?) the "jail" additions were >>>>> also >>>>> added at different times, and by different people. So I'd imagine that >>>>> unless someone with a commit bit decides one day they'd like to take >>>>> that >>>>> on. Someone(tm) maybe you? will need to propose a patch. :-) >>>> >>>> >>>> >>>> If I can understand C sources I will create the patch by myself >>>> instead of just posting here. Unfortunately I am able to code in sh, >>>> php and a bit of javascript and perl but no C. :) >>>> >>>> Miroslav Lachman >>> >>> >>> >>> Sure, a PR would be handy for this - it's a pretty simple thing to add, >>> and >>> consistency would indeed be a good move. >> >> >> Agreed. I'll review and commit such patches. I'd like to see a single >> function for taking a "id or name". Ideally it would live in a >> library, perhaps libjail? > > > It already lives there: jail_getid(3) I was thinking of a more generic one that does id or name. Now that I think about it a bit more, C makes this kind of thing impossible to do usefully. That said, I'll still review and commit any patches to existing tools to make them behave consistently. -- Eitan Adler ___ 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: jail related inconsistencies in FreeBSD tools parameters
On 23 June 2018 at 08:30, James Gritton wrote: > On 2018-06-22 16:03, Miroslav Lachman wrote: >> >> Chris H wrote on 2018/06/22 23:46: >>> >>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz> >>> said >>> >>>> I don't know if it is better to discuss it in jail@ or stable@ list so a >>>> do cross-post. >>>> >>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>> taking JID as parameter. >>>> >>>> For example "sockstat" takes -j JID "Show only sockets belonging to the >>>> specified jail ID" and it means numeric ID only. >>>> On the other hand "ps" takes -J JID "This may be either the jid or name >>>> of the jail. Use -J 0 to display only host processes." >>>> The same apply for "top", it understands jid as a number or name of the >>>> jail too. >>>> Then again "cpuset" takes only numerical ID of the jail... >>>> >>>> Shouldn't it be consistent across all FreeBSD base utilities so all of >>>> them can use numerical ID and name? >>> >>> Good idea! Are you offering to create a patch? ;-) >>> It'd be my guess that given they weren't all created at the same time, >>> nor >>> the same individual; that (quite probably?) the "jail" additions were >>> also >>> added at different times, and by different people. So I'd imagine that >>> unless someone with a commit bit decides one day they'd like to take that >>> on. Someone(tm) maybe you? will need to propose a patch. :-) >> >> >> If I can understand C sources I will create the patch by myself >> instead of just posting here. Unfortunately I am able to code in sh, >> php and a bit of javascript and perl but no C. :) >> >> Miroslav Lachman > > > Sure, a PR would be handy for this - it's a pretty simple thing to add, and > consistency would indeed be a good move. Agreed. I'll review and commit such patches. I'd like to see a single function for taking a "id or name". Ideally it would live in a library, perhaps libjail? -- Eitan Adler ___ 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: Ryzen issues on FreeBSD ? (with sort of workaround)
On 20 April 2018 at 04:15, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by the speed and went home. > > ...and by the time I got home, an hour or so later, it had locked up hard. ... I have a Ryzen system parts: https://pcpartpicker.com/list/HhycYT dmesg: http://dmesgd.nycbug.org/index.cgi?do=view&id=3516 which I have been using for months without issue and on completely default settings. What mobo do you have? Did you update the BIOS to the latest version? -- Eitan Adler ___ 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: Stability of 11.1S
On 19 March 2018 at 22:59, Dewayne Geraghty wrote: > Hi Eitan, > Agreed. Unfortunately all I have is that it abruptly shuts down. Both > under load (10,8,?) - during a full package rebuild (~1200 ports); and > during periods of idleness between 1am-2am. From our console.log there are > approximately 6 MARK entries in the logs, so it can be idle for that period > of time (2 hours) before halting, abruptly. There has been some additional conversation but just wanted to pick something to reply to: I will take full ownership if something I've MFCed caused breakage. That said I'm somewhat stuck unless I am able to reproduce the issue, or at least guess as to the cause. > PS Normally I would bisect, but we're converting 2 large PROLOG applications > to erlang... (prayers welcome) Both fun languages. -- Eitan Adler ___ 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: Stability of 11.1S
On 19 March 2018 at 18:05, Dewayne Geraghty wrote: > We rebuild 11.1-Stable at least every two weeks. Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > r329008. Is anyone actually running a Stable that was built after 22nd > Feb? Could you please share the revision number? > > Because the churn in > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > high we haven't been able to sight if a problem was identified and > fixed; so we're really looking for a functioning stable that we can > resume tracking. Hi, I can't help identify the problem and if it was fixed without any information. Can you at least let us know what kind of crashes are you seeing? Kernel panics?SIGBUS? Something else? It would be best if you could bisect to the revision causing you problems. Note that despite the name, STABLE is a development branch and users of the branch are expected to be able to provide some help tracking down issues. -- Eitan Adler ___ 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: build kernel failure stable11 iwi related
On 1 March 2018 at 05:34, Trond Endrestøl wrote: > On Thu, 1 Mar 2018 14:09+0100, Trond Endrestøl wrote: > >> If you revert to r330229, i.e. svn up -r330229 /usr/src, you should be >> able to build a working kernel. >> >> r330230 added "17" to line 1939 of sys/conf/files breaking iwm(fw), >> and I suspect "17" should be "22", or maybe the "D" should be removed. >> >> r330233 caused the errors you reported. >> >> I hope these errors will be corrected shortly. Build error is fixed. Sorry for the breakage > r330229 is also broken. I had to revert to r330113 to avoid any of the > recent iwm commits. Did r330242 fix the issue for you? -- Eitan Adler ___ 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: Some PR never seen to delete
On Sun, Sep 1, 2013 at 3:53 AM, David Demelier wrote: > On 30.08.2013 22:30, Jakub Lach wrote: >> Why would you want to have valid ones closed? >> > > They are not all valids anymore. For these, they should be closed. I closed 2010/09/16 kern/150628 [acd] [ata] burncd(1) can't write to optical drive 2011/01/25 ports/154288 glewis[patch] games/nethack*: remove old ports and cleanup latest 2012/12/23 ports/174650 xfcex11-wm/xfce4 crash with Which of the others are completely invalid now (as opposed to just old?) >For the other, they are > almost 3 years old. Merely being old doesn't mean they won't be fixed: I have committed fixes for 10 year old PRs. ;) -- Eitan Adler ___ 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"
Re: FreeBSD history
On Sun, Jun 16, 2013 at 7:00 PM, Andy Farkas wrote: > On 16/06/13 20:30, Jeremy Chadwick wrote: >> * Output from: strings /boot/kernel/kernel | egrep ^option Thanks. > > I stumbled across this one about a week ago: > > strings /boot/kernel/kernel | head -1 It seems peter@ added this in r39818 during 1998-09-30. Perhaps he would know more? > Is not a celebration / announcement warranted? I've added a notice to the news page a few days ago. Thanks for the info! -- Eitan Adler ___ 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"
Re: bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
On 10 May 2013 16:59, Ronald F. Guilmette wrote: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 > > It has been suggested to me (by a committer) that I should raise the > issue of this PR here on these lists, because the problem described > within the PR remains a real problem, and despite my having proposed > something that seems to be a perfectly workable fix, no action has > been taken on this PR for some years now. By the way, it will go a long way to helping get some site on these PRs, if you provide diffs in 'unified diff' form (diff -u) instead of context diff form. I have been recently looking for old PRs with patches attached. :) -- Eitan Adler ___ 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"
Re: Incomplete r249912
On 26 April 2013 08:05, Glen Barber wrote: > On Fri, Apr 26, 2013 at 09:15:34AM +0200, Trond Endrestøl wrote: >> r249912, MFC r249802, is incomplete. >> >> Please fix stable/9/lib/libc/gen/stringlist.c or amend >> stable/9/include/stringlist.h. The latter is preferred. >> > > I just fixed this. I merged both, but forgot to do "svn ci" at the root. Sorry for the breakage. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams ___ 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"
Re: svn revision stable/9
On 23 April 2013 09:38, Kimmo Paasiala wrote: > On Tue, Apr 23, 2013 at 3:42 PM, John Mehr wrote: >> >> >> Hello, >> >> svnup stores "known file" information in /tmp/svnup for each of the defined >> sections (current, stable, ports, etc.) and in the next update, it will be >> including the revision number in these files so that something like: >> >> # svnup stable -n >> >> would return the stable branch's last downloaded revision number and then >> exit. >> >> Because the current, stable and releng branches all use /usr/src by default, >> implementing a custom svnversion to inform newvers.sh of which revision >> exists in /usr/src would be problematic without leaving a small bread crumb >> there for newvers.sh to use. If this is ok to do, I can include this in the >> next revision (which should be ready to go in the next couple of days). >> > > Wouldn't /var/db/svnup be the proper place for the "bread crumb"? There may be multiple source trees. newvers.sh looks at the current source tree to determine which version to use. -- Eitan Adler ___ 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"
Re: CLANG and -fstack-protector
On 12 February 2013 21:22, Dmitry Marakasov wrote: > If there's interest in this, I can refresh the patch and submit it. Yes. Please do! -- Eitan Adler ___ 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"
Re: setfacl man page states "d=delete_child" and "D=delete"
On 8 February 2013 13:46, Edward Tomasz Napierała wrote: > Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 16:08: >> Hello, >> >> I think there's a confusion in the man page setfacl(1). >> >> In my tests, "D" means "delete_child" and "d" "delete"; like it's true >> for other NFSv4 implementations. But manpage tells the other way around. > > Fixed the man page, thanks! There are more errors. Please see the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/174433 -- Eitan Adler ___ 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"
Re: CLANG and -fstack-protector
On 7 February 2013 18:40, Kimmo Paasiala wrote: >> Ports are largely independent of the base system, and their compilation >> flags are different from port to port. You could set -fstack-protector >> for your ports in either make.conf or ports.conf, if you wanted. > > Is there any work being done to provide an optional Makefile knob > (WITH_STACK_PROTECTOR ?) to turn on -fstack-protector for ports that > install network services (or other critical code)? I'd bet such > feature would be popular. As far as I am aware no such feature exists. In any case it would be subject to the same problem of many ports ignoring CFLAGS and friends. -- Eitan Adler ___ 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"
Re: countdown from 31: helping with the FAQ
On 28 January 2013 15:16, John Nielsen wrote: > Cherry-picking a few: Awesome. Thanks for the comments. I've added them to the wiki page. Would you like an account? 23 unreviewed questions left! About 70 questions awaiting patches. -- Eitan Adler ___ 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"
countdown from 31: helping with the FAQ
Hey all, I've been working for past several months on improving the FAQ. At the moment there are 31 unreviewed questions. Can you all help out by commenting on the yellow questions here: https://wiki.freebsd.org/ThwackAFAQ - once the review stage is done we could continue fixing the red ones! -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 3 January 2013 16:19, Glen Barber wrote: > On Thu, Jan 03, 2013 at 04:12:32PM -0500, Eitan Adler wrote: >> I think everyone agrees there is room for a svnup like program which >> has a read-only svn mode to download and update sources with minimal >> (zero?) dependencies. >> >> That said, someone has to write it. >> > > http://svnweb.freebsd.org/base/user/des/svnsup/ Yes. I was talking about this. $someone needs to step up and complete it. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 3 January 2013 16:04, Lev Serebryakov wrote: > Hello, Matthew. > You wrote 4 января 2013 г., 0:39:33: > > MS> Ah. Yes, you are right. You can't track a stable branch with > MS> freebsd-update. In that case, svn is the way to go. > And even as developer I don't like this situation. My developer > systems have and could use svn for sure, but servers? csup was very > handy for non-developers machines. I think everyone agrees there is room for a svnup like program which has a read-only svn mode to download and update sources with minimal (zero?) dependencies. That said, someone has to write it. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 3 January 2013 13:57, Lee Dilkie wrote: > but that fetches binaries, not sources. It does both. It can be configured to update just one or the other as well. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 3 January 2013 02:32, Matthias Andree wrote: > Please do not quote addresses. Not all web archives and copies hide > them properly. Hiding email addresses is useless for spam control. Obfuscating them makes it harder to follow a conversation. > Regarding versions, please read the relevant information: > the relevant decision was made years ago, and the version number you > slap at the switch is a moot point. CVS/SVN should be considered a development tool. Users should not see the impact of the switch. In theory. > A "long list [of sites] for CVS" is required to overcome load problems. ... > Updates are much > quicker IMO than they ever were with CVS, even with a local c[v]sup copy > of the CVS sources on the same computer. There are latency issues with svn servers only in the US. There is work underway to obtain more mirrors outside the US. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 2 January 2013 06:26, Chris Rees wrote: > To clarify, no-one wants to remove CVS completely, the suggestion was to > move it out of the base system. As the developer responsible for this: CVS will be removed from base. It already exists as a port in devel/cvs -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 1 January 2013 15:17, Alfred Perlstein wrote: > On 1/1/13 6:55 AM, Eitan Adler wrote: >> >> On 1 January 2013 02:54, Derek Kulinski wrote: >>> >>> That said I would totally understand you being upset if FreeBSD would >>> decide to switch to git, since despite its benefits that is a huge >>> change, and would definitely be hard for people to adjust. >> >> Just In Case: >> >> FreeBSD has no plans to switch to get in either the short or long >> term. We will however offer git repositories and first-class cousins >> via git.freebsd.org and github. >> >> > Are you sure? Most of the diffs developers have been handing me lately are > of the form a/path b/path so I think they are mostly using git behind the > scenes. Yes. I use git behind the scenes as well. However, so far as I am aware, there are no plans in either the short or long terms to *convert upstream* to git. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 1 January 2013 02:54, Derek Kulinski wrote: > That said I would totally understand you being upset if FreeBSD would > decide to switch to git, since despite its benefits that is a huge > change, and would definitely be hard for people to adjust. Just In Case: FreeBSD has no plans to switch to get in either the short or long term. We will however offer git repositories and first-class cousins via git.freebsd.org and github. -- Eitan Adler ___ 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"
Re: Does / Is anyone maintaining CVS for FreeBSD?
On 31 December 2012 15:40, Chris H wrote: > Sigh... > IM(NS)HO; SVN is an inferior RCS created so Windows users wouldn't feel > left out. SVN has a number of features which makes development much easier. What did you find easier to accomplish with CVS than with SVN? > Are there _any_ CVS servers/trunks/tree's left? If so, how _current_ are > they? Ports and Source currently have CVS trees. Ports has an explicit EoL on February 28th (2 months from today) Source does not have an explicit EoL though it *is* considered deprecated. -- Eitan Adler ___ 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"
Re: What is "negative group permissions"? (Re: narawntapu security run output)
On 24 December 2012 10:27, jb wrote: > Those security checks are for a reason - people make mistakes (even a perfect > guy like you will have a "head in a brown bag" time). > It is better to get a heads-up, then think about it and turn it off > (customize) > if considered unneeded. +1. Default to helping the new user (or the user that makes mistakes). -- Eitan Adler ___ 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"
Re: No more torrents.....
On 18 December 2012 03:59, Willem Jan Withagen wrote: > So what is the reason for this? The software used to seed the torrents was horribly insecure. This was found *prior* to the security incident. > policy > no more support? I have been trying to convince re@ and clusteradm@ to produce "web seed" torrents using the same mirrors we have now. I imagine further progress could be made after the 9.1 release. -- Eitan Adler ___ 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"
Re: How do I circumvent the use of clang during build?
On 16 December 2012 21:17, Tim Daneliuk wrote: > As I understand it, gcc is still the default on 9 For the build, but clang is still built. > is it possible >>to build(world|kernel) && install(world|kernel) without the >>clang toolchain? make -DWITHOUT_CLANG -- Eitan Adler ___ 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"
Re: Will we get a RELEASE-9.1 for Christmas?
On 9 December 2012 08:48, Jakub Lach wrote: > This is good answer for end users, not so much when > somebody is genuinely concerned if there were some > unforeseen issues. Agreed. Companies need predictability. FWIW: The ports tree is open now (ports branch was tagged). The 9.1.0 src branch was tagged already. I'd expect to be released *very* shortly (before Christmas), although I don't know an exact date. -- Eitan Adler ___ 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"
Re: Help review the FAQ
On 7 December 2012 16:11, Bas Smeelen wrote: > On 12/07/12 21:36, Jakub Lach wrote: >> >> While it's very, very minute detail, I think that in #officesuite >> there should be "Apache OpenOffice" not "Apache Open Office" >> as they were very careful even bureaucratic [*] if I reckon correctly, >> when choosing new branding. >> >> [*] They have "branding initiative guidelines" and held vote- >> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache Patch sent to mentor for approval. Thanks! -- Eitan Adler ___ 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"
Re: Some new hardware with 9.1 does not reboot easily
On 29 November 2012 10:16, Willem Jan Withagen wrote: > On 2012-11-29 16:08, Andriy Gapon wrote: >> on 29/11/2012 10:53 Willem Jan Withagen said the following: >>> On 2012-11-29 9:41, Patrick Lamaiziere wrote: >>>> Le Mon, 26 Nov 2012 12:19:07 +0200, >>>> Andriy Gapon a écrit : >>>> >>>> Hello, >>>> >>>>> on 26/11/2012 12:10 Patrick Lamaiziere said the following: >>>>>> As far I can see it fails because there is no getnewvnode_reserve() >>>>>> / get_newvnode_drop_reserve() in 9.1. >>>>> >>>>> The patch is for stable/9. >>>> >>>> Ok, thanks. >>>> >>>> I've made a new diff because Willem's patch does not apply >>>> on 9.STABLE (fails on opensolaris_lookup.c) : >>>> >>>> This one is for 9-stable rev 243569: >>>> http://user.lamaiziere.net/patrick/9-STABLE-r243569-patch-zfs-reboot >>>> >>>> It solves the reboot problem on my server. I'm testing it on my >>>> workstation with few "poudriere bulk". It looks to work. >> >> Thank you very much for testing! >> >>> Andriy sent me his diff aginst HEAD, which I reworked against the code I >>> have here locally. I did an svn diff against the checkout of that >>> morning. And I'm pretty sure i'm tracking stable/9 >>> >>> So I'm not sure where I went wrong, but thanx for fixing it. >> >> I MFC-ed some ZFS changed from HEAD last weekend. > > Would that mean that the regular checkout of stable/9 contains enough > code to allow "painless" rebooting... > > Reason I ask: > I'm about to ship the server to the customer > > But there is still 45 minutes before UPS comes to pick it up. > And I'd rather run a regular checkout, instead of the patched one. > > Which then gets me to the svn question: > How do I easily get ride of the changeds? If I understand what you want correctly, just run 'svn revert -R .' -- Eitan Adler ___ 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"
Re: Help review the FAQ
On 26 November 2012 11:25, Jakub Lach wrote: > Thanks! > > Regarding FAQ, some info about journalling should be added to > "Chapter 9 Disks, File Systems, and Boot Loaders", especially now, > when SU+J is default. which question does this apply to, or is this a request for new questions? -- Eitan Adler ___ 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"
Re: Help review the FAQ
On 25 November 2012 13:28, Jakub Lach wrote: > Why is my kernel so big? > > "As long as you make sure you follow the steps above, you can build your > kernel normally, and you should notice a fairly large size decrease; most > kernels tend to be around 1.5 MB to 2 MB." > > Not really, stripped amd64 kernel is about 9 MB currently... Is this the size of GENERIC on release media? -- Eitan Adler ___ 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"
Re: Help review the FAQ
On 19 November 2012 15:07, Aldis Berjoza wrote: > > > 19.11.2012, 22:04, "Andrea Venturoli" : >> On 11/19/12 18:44, Eitan Adler wrote: >> >>> Hey all, >>> >>> The FAQ for FreeBSD needs a significant amount of updating and >>> changing. The first step in that process is to figure out what needs >>> to be changed. >>> >>> If you can a take a moment and thoroughly review just one >>> question and add your comments and concerns it >>> would be immensely helpful. >>> >>> http://wiki.freebsd.org/ThwackAFAQ ... I've migrated the comments on the mailing list to the wiki and will working on fixing them shortly. Content patches are appreciated but not required. Ideally every row on the wiki will be either green or red. Fixing the content is a very long term project. -- Eitan Adler ___ 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"
Re: Node conflicts in SVN
On 19 November 2012 21:43, Frank Seltzer wrote: > > > On Mon, 19 Nov 2012, Kevin Oberman wrote: > >> On Mon, Nov 19, 2012 at 11:37 AM, Frank Seltzer >> wrote: >>> >>> >>> >>> On Mon, 19 Nov 2012, Kevin Oberman wrote: >>> >>>> On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer >>>> wrote: >>>>> >>>>> >>>>> I run a nightly ports tree update and I have been getting the following >>>>> errors the last couple of days. I haven't seen this asked before so is >>>>> this >>>>> just me or is anyone else seeing this? Have I fat-fingered something? >>>>> >>>>> Updating '/usr/ports': >>>>> Skipped '/usr/ports/astro' -- Node remains in conflict >>>>> Skipped '/usr/ports/devel' -- Node remains in conflict >>>>> Skipped '/usr/ports/sysutils' -- Node remains in conflict >>>>> Skipped '/usr/ports/audio' -- Node remains in conflict >>>>> Skipped '/usr/ports/textproc' -- Node remains in conflict >>>>> Skipped '/usr/ports/x11-fm' -- Node remains in conflict >>>>> Skipped '/usr/ports/MOVED' -- Node remains in conflict >>>>> Skipped '/usr/ports/games' -- Node remains in conflict >>>>> Skipped '/usr/ports/mail' -- Node remains in conflict >>>>> Skipped '/usr/ports/net' -- Node remains in conflict >>>>> Skipped '/usr/ports/multimedia' -- Node remains in conflict >>>>> At revision 307524. >>>>> Summary of conflicts: >>>>> Skipped paths: 11 > > > It's now up to 24. > > Updating '/usr/ports': > > Skipped '/usr/ports/mail' -- Node remains in conflict > Skipped '/usr/ports/net' -- Node remains in conflict > Skipped '/usr/ports/multimedia' -- Node remains in conflict > Skipped '/usr/ports/dns' -- Node remains in conflict > Skipped '/usr/ports/www' -- Node remains in conflict > > Skipped '/usr/ports/astro' -- Node remains in conflict > Skipped '/usr/ports/sysutils' -- Node remains in conflict > Skipped '/usr/ports/devel' -- Node remains in conflict > Skipped '/usr/ports/audio' -- Node remains in conflict > Skipped '/usr/ports/textproc' -- Node remains in conflict > Skipped '/usr/ports/japanese' -- Node remains in conflict > Skipped '/usr/ports/graphics' -- Node remains in conflict > Skipped '/usr/ports/security' -- Node remains in conflict > > Skipped '/usr/ports/x11-fm' -- Node remains in conflict > Skipped '/usr/ports/MOVED' -- Node remains in conflict > Skipped '/usr/ports/irc' -- Node remains in conflict > Skipped '/usr/ports/math' -- Node remains in conflict > > Skipped '/usr/ports/games' -- Node remains in conflict > Skipped '/usr/ports/archivers' -- Node remains in conflict > Skipped '/usr/ports/deskutils' -- Node remains in conflict > Skipped '/usr/ports/net-p2p' -- Node remains in conflict > Skipped '/usr/ports/databases' -- Node remains in conflict > Skipped '/usr/ports/net-mgmt' -- Node remains in conflict > Skipped '/usr/ports/net-im' -- Node remains in conflict > At revision 307575. > Summary of conflicts: > Skipped paths: 24 did you run svn checkout on a directory which wasn't controlled by svn (with stuff in it?). If so you need to remove those directories and run "svn up". -- Eitan Adler ___ 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"
Help review the FAQ
Hey all, The FAQ for FreeBSD needs a significant amount of updating and changing. The first step in that process is to figure out what needs to be changed. If you can a take a moment and thoroughly review just one question and add your comments and concerns it would be immensely helpful. http://wiki.freebsd.org/ThwackAFAQ -- Eitan Adler ___ 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"
Re: confirm that csup is still usable fos the new 9.1
On 16 November 2012 11:25, Edwin L. Culp W. wrote: > I haven't received updates to sources, ports or release for a few days. > The process seems to work, no errors, but no updating. There are known problems with the cluster at this time. The machines were recently moved, upgraded, and generally manipulated. We are working to fix this as fast as possible. -- Eitan Adler ___ 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"
Re: Compilation error while compiling FreeBSD9-STABLE with Clang
On 14 November 2012 20:40, Alie Tan wrote: > Hi, > > Strange, this issue happens when I use cvsup only. Did I miss something > here? Is FreeBSD CVS still syncing with SVN or otherwise? known issue atm. people are working on fixing it. -- Eitan Adler ___ 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"
Re: FreeBSD in Google Code-In 2012? You can help too!
On 24 October 2012 13:24, Fernando Apesteguía wrote: > Also related to that, what about writing a section about redports[1] > in the porter's handbook[2]? This is a good documentation task... but we need more *coding* tasks as well. > And as a side question, shouldn't some (or all) of these tasks be > listed also in JuniorTasks[3]? I'll link the page: good point. -- Eitan Adler ___ 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"
Re: pty/tty or signal strangeness, or grep/bsdgrep bug?
On 23 October 2012 22:40, Jeremy Chadwick wrote: > No problem folks. Would you like me to file a PR for this so we can > track it/for historical purposes? yes please -- Eitan Adler ___ 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"
Re: FreeBSD in Google Code-In 2012? You can help too!
On 23 October 2012 13:11, Adrian Chadd wrote: > So where are examples of what other successful open source projects have done? There are tasks done by the winner last year: https://www.google-melange.com/gci/student_tasks/google/gci2011/dragooon Here are all the tasks last year: https://www.google-melange.com/gci/tasks/google/gci2011 -- Eitan Adler ___ 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"
Re: FreeBSD in Google Code-In 2012? You can help too!
On 23 October 2012 12:54, David Magda wrote: > On Tue, October 23, 2012 10:39, Fbsd8 wrote: >> >> The subject is Google Code-In and all the posted tasks are directed at >> creating documentation. Not one deals with coding any programs. If I was >> 15-17 years old I sure would not be interested in writing documentation. >> I would want to use and develop my coding skills. To that end there a >> lot of simple PR's waiting for attention. This is an target area that >> young coders would find more interesting. > > It would depend on what one's interests were. Google code-in is aimed at *coders* and there is an expectation of people writing *code*. The biggest complaint for GCI last year was "not enough coding tasks" -- Eitan Adler ___ 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"
Re: Missing lib on linking libc WITH_LIBCPLUSPLUS
On 2 October 2012 12:01, Volodymyr Kostyrko wrote: > 02.10.2012 12:12, Dimitry Andric wrote: >> >> On 2012-10-02 09:53, Volodymyr Kostyrko wrote: >>> >>> When enabling WITH_LIBCPLUSPLUS libc build fails with: >>> >>> /usr/local/libexec/ccache/clang++ -O2 -pipe -march=native >>> -I/usr/src/lib/libc++/../../contrib/libc++/include >>> -I/usr/src/lib/libc++/../../contrib/libcxxrt -nostdlib -DLIBCXXRT >>> -Qunused-arguments -fstack-protector -Wno-empty-body >>> -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value >>> -Wno-parentheses-equality -Wno-unused-function -Wno-conversion >>> -Wno-switch -Wno-switch-enum -Wno-parentheses -std=c++0x -c >>> cxxrt_guard.cc -o cxxrt_guard.o >>> building shared library libc++.so.1 >>> FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 >>> Target: x86_64-unknown-freebsd9.0 >>> Thread model: posix >>>"/usr/bin/ld" --eh-frame-hdr -Bshareable -o libc++.so.1 >>> /usr/lib/crti.o /usr/lib/crtbeginS.o -L/usr/lib -x --fatal-warnings >>> --warn-shared-textrel -soname libc++.so.1 valarray.So utility.So >>> typeinfo.So strstream.So regex.So random.So iostream.So debug.So >>> chrono.So bind.So algorithm.So hash.So thread.So future.So exception.So >>> locale.So mutex.So memory.So ios.So condition_variable.So >>> system_error.So string.So stdexcept.So new.So -lcxxrt -lgcc --as-needed >>> -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed >>> /usr/lib/crtendS.o /usr/lib/crtn.o >>> /usr/bin/ld: cannot find -lcxxrt >>> clang: error: linker command failed with exit code 1 (use -v to see >>> invocation) >>> >>> This lib was already built: >>> >>> # find /usr/obj -name libcxxrt.so >>> /usr/obj/usr/src/tmp/usr/lib/libcxxrt.so >>> /usr/obj/usr/src/lib/libcxxrt/libcxxrt.so >>> >>> But this error is only fixed after: >>> >>> # cd /usr/src/lib/libcxxrt ; make install >> >> >> Are you getting this error as part of buildworld, or when you build >> libc++ by hand? > > > As part of the buildworld. I feel that it looks for the lib in the system > skipping /usr/obj. > > >> Also, an obvious question is: does it work when you disable ccache? > > > Bingo. Yes, disabling ccache makes everything work. please ping the ccache folk about this. It *shouldn't* matter. :) -- Eitan Adler ___ 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"
Re: how to update ports while using pkgng?
On 15 September 2012 17:44, Jamie Paul Griffin wrote: > [ Freddie Cash wrote on Fri 14.Sep'12 at 21:54:29 -0700 ] > >> Read the pkgng faq online. There's a link to a patch for portmaster, and >> info on what to add to make.conf. > > Can I ask: why is it still necessary for us to patch portmaster, can this not > be implemented using an option during `make config` when installing > portmaster or updating it, etc.? The maintainer of portmaster does not believe the patch to be of sufficient quality to make it into the mainstream release. It should be considered a "third party hack" for now. -- Eitan Adler ___ 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"
Re: Weird message in dmesg
On 27 August 2012 09:47, Dag-Erling Smørgrav wrote: > Eitan Adler writes: >> "Dag-Erling Smørgrav" writes: >> > On an amd64 system, you should just set it to 0. >> Can we put this advice into the printf? > > There is no need for that, as 0 is already the default for amd64 in > head, and I intend to MFC that change very soon. good enough :) -- Eitan Adler ___ 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"
Re: Weird message in dmesg
On 27 August 2012 05:50, Dag-Erling Smørgrav wrote: > OriS writes: >> "Dag-Erling Smørgrav" writes: >> > On an amd64 system, you should just set it to 0. >> Well, maybe it'd be a good idea to set it to 0 on amd64 systems for >> amd64-RELEASE's. Can we put this advice into the printf? -- Eitan Adler ___ 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"
Re: Who is responsible for Heimdal/Kerberos in FreeBSD
On 3 August 2012 04:51, Attila Bogár wrote: > On 02/08/12 16:04, Chris Nehren wrote: > However I think, it's more sad, that the freebsd developer community is just > ignoring the patches they are sent and doesn't considers quality assurance. I understand your frustration, having patches that you think are good sitting for two years isn't fun for anyone. On the other hand your statement that we ignore patches and don't care is bogus: http://www.oook.cz/bsd/prstats/arriverates.html http://www.oook.cz/bsd/prstats/closerates.html Something you need to remember is that the developers are no more responsible to fix bugs than you are. We make an effort to do so, and we have improvements in the process to make, but please don't claim we intentionally ignore patches that are sent or don't care. -- Eitan Adler ___ 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"
Re: The MFC process...
On 17 July 2012 10:10, Warren Block wrote: >> I have a special place in my email for MFC reminder emails which I use >> as a "todo" list. Getting weekly reminders would just be annoying. > > Why would it be a problem with with MFCs if it isn't a problem for PRs? Some people find the PR ones annoying. ;) A better answer: because sometimes I make a deliberate decision to *not* MFC something even though it says "MFC after" > Unless there was no PR. Which brings up the question of how can we query > for MFCs now? For example, how many MFCs are past due? What is the oldest > one? svn mergeinfo --show-revs eligible The OP seemed interested in writing a script to make this output usable. -- Eitan Adler ___ 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"
Re: The MFC process...
On 17 July 2012 09:53, Warren Block wrote: > I don't expect it to happen. But right now, there's only the initial mail > that the MFC is due, and no reminder afterwards. We have the open PR mails > once-weekly; MFCs are at least as important. I have a special place in my email for MFC reminder emails which I use as a "todo" list. Getting weekly reminders would just be annoying. > Come to think of it, entering PRs for past-due MFCs could be a way to do > that with the existing systems. We have this already: PRs in the 'patched' state. -- Eitan Adler ___ 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"
Re: The MFC process...
On 17 July 2012 09:28, Warren Block wrote: > On Tue, 17 Jul 2012, Eitan Adler wrote: > >> On 17 July 2012 05:50, David Magda wrote: >>> >>> On Tue, July 17, 2012 02:10, Eitan Adler wrote: >>>> >>>> Of interest to me: if it could be limited to just the commits I made >>>> and optionally show me the log message and diff it would be very >>>> helpful. >>>> >>>> On a general note: be careful with any level of automation with this >>>> script though. Sometimes there are good reasons that a commit wasn't >>>> MFCed. >> >> >> >>> A lot of messages have a "MFC after" note on them, so the the developer/s >>> in question already know which commits are good candidates for bringing >>> over to STABLE. It may simply be that they could use a reminder on them. >> >> >> Just to add: developers get an automated email at the "MFC after" time >> reminding them to MFC. > > > But only once. It would be nice if it was like PR notifications, once a > week. Please no! If this is the case, it should be an option. -- Eitan Adler ___ 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"
Re: The MFC process...
On 17 July 2012 05:50, David Magda wrote: > On Tue, July 17, 2012 02:10, Eitan Adler wrote: >> Of interest to me: if it could be limited to just the commits I made >> and optionally show me the log message and diff it would be very >> helpful. >> >> On a general note: be careful with any level of automation with this >> script though. Sometimes there are good reasons that a commit wasn't >> MFCed. > A lot of messages have a "MFC after" note on them, so the the developer/s > in question already know which commits are good candidates for bringing > over to STABLE. It may simply be that they could use a reminder on them. Just to add: developers get an automated email at the "MFC after" time reminding them to MFC. -- Eitan Adler ___ 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"
Re: The MFC process...
On 16 July 2012 22:35, Trent Nelson wrote: > On 7/16/12 11:19 PM, "Eitan Adler" wrote: > >>On 16 July 2012 19:33, Trent Nelson wrote: >>> >>> There are currently no automated MFC systems in place, correct? I.e. >>>the >>> onus is completely on the developer that made the change to head to >>>merge >>> back to stable? >> >>Correct. >> >>> Do the RELENG team do anything in particular to check >>> that changes for MFC actually make it back to stable? >> >>As far as I am aware, they do not. > > Sounds like a "what-hasn't-been-MFC'd-back-to-stable-yet" script could be > quite useful, then ;-) Of interest to me: if it could be limited to just the commits I made and optionally show me the log message and diff it would be very helpful. On a general note: be careful with any level of automation with this script though. Sometimes there are good reasons that a commit wasn't MFCed. -- Eitan Adler ___ 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"
Re: The MFC process...
On 16 July 2012 19:33, Trent Nelson wrote: > > There are currently no automated MFC systems in place, correct? I.e. the > onus is completely on the developer that made the change to head to merge > back to stable? Correct. > Do the RELENG team do anything in particular to check > that changes for MFC actually make it back to stable? As far as I am aware, they do not. > Reason for asking, I noticed a bit of disparity between dev/isp between > head and stable/9: > ... > I'm currently running a local tree with those revs merged in manually > (simply via `svn merge svn://svn.freebsd.org/base/head/sys/dev/isp .` in > /usr/src/sys/dev/isp), but it'd be nice to get them into 9.1, as they're > all past their recommend soak time (except for that last one, which is a > typo fix). We are currently in a code freeze for 9.1 so no unapproved MFCs may be committed. > Anyway, that got me thinking about the MFC process, especially leading up > to another release, hence this e-mail. What's the preferred way for > non-committers to bring outstanding MFCs to the attention of committers? Exactly the way you did it here: a polite email. :) -- Eitan Adler ___ 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"
Re: Why Are You NOT Using FreeBSD ?
On 1 June 2012 23:33, Zach Leslie wrote: >> So ZFS can ensure that bits-on-disk stay safe through checksums and >> mirroring / RAIDZ, while Gluster allows entire file servers to go offline >> and the files are still accessible because you have a kind of network-level >> RAID going on. This also helps in performance since instead of clients >> pounding on one file server (as usually happens with NFS), every write is >> sent to many data nodes so you're striping across many network elements. >> Think of it as NFS on steroids. > > I don't know that new work in distributed filesystems, like Ceph > (http://ceph.com/), is inherently tied to Linux, but more that devs are > choosing Linux as a platform on which to build awesome projects. The question to ask here is what utilities, APIs, and features does Linux have which cause developers to use it instead and what could we do about it? -- Eitan Adler ___ 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"
Re: -DNO_CLEAN compiling & recent changes as of ~two weeks.
On 29 April 2012 13:31, Jason Hellenthal wrote:
>
> Somewhere is the last two weeks it seems something has changed on
> 8-STABLE that causes a complete rebuild of the kernel every time it is
> built.
>
> While this is not too much of a problem, it is quite a neusense when
> attempting to make a quick change that would only require a recompile of
> the effected code and relink that would only amount to about 5 or 10
> minutes.
>
> I am running FreeBSD 8.3-STABLE #0 r234692 i386 where this has been an
> issue. The earliest part of the kernel I always see compile is ACPI code
> if that helps to determine the problem.
>
> A few committs that I picked out that might cause it but only a guess
> is... (I could be wrong about these)
>
> After 8.3-RELEASE
> r234634
> r234631
> r234604
>
> Before 8.3-RELEASE
> r234534
> r234512
> r234509
>
> Maybe just a text or data relocation issue ? Has anyone else noticed this ?
>
>
> To test after a full build of kernel #0.
>
> 1) Change config ROUTETABLES={ROUTETABLES+1}
> 2) cd /usr/src
> 3) time -h make -DNO_CLEAN buildkernel
use -DKERNFAST or -DNO_KERNELCLEAN
--
Eitan Adler
___
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"
Re: top not restoring terminal echo/icanon correctly
On 17 April 2012 21:25, Jeremy Chadwick wrote: > Thoughts/comments? Should I close my existing PR and open a new one? Please submit the fix to bin/161739. If you can please submit two different diffs: the first which fixes the problem, the second with is general cleanup as a separate PR. CC me on the submission. The goal is keep the patch and your analysis together for future reference. -- Eitan Adler ___ 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"
Re: environment declared, yet problem to compile HipHop in FreeBSD9-RELEASE
On 17 April 2012 15:12, Zenny wrote: > On 4/17/12, Eitan Adler wrote: >> On 17 April 2012 15:03, Zenny wrote: >>> Using csh, so I used set VAR. setenv didn't work. >> >> set sets shell options. setenv sets environment variables. What didn't work? >> > # setenv HPHP_HOME=`pwd` > setenv: Syntax Error. You are attempting to use bash/zsh syntax with tcsh. try setenv HPHP_HOME `pwd` -- Eitan Adler ___ 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"
Re: environment declared, yet problem to compile HipHop in FreeBSD9-RELEASE
On 17 April 2012 15:03, Zenny wrote: > Using csh, so I used set VAR. setenv didn't work. set sets shell options. setenv sets environment variables. What didn't work? -- Eitan Adler ___ 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"
New feature: support for ASCII art splash screens in TheDraw format (svn commit r229994)
I just committed this feature which some of you may be interested in Example .bin files here: http://www.mawer.org/freebsd/ -- Forwarded message -- From: Eitan Adler Date: Wed, Jan 11, 2012 at 7:02 PM Subject: svn commit: r229994 - in stable/9: share/man/man4 sys/dev/fb sys/modules/splash sys/modules/splash/txt To: src-committ...@freebsd.org, svn-src-...@freebsd.org, svn-src-sta...@freebsd.org, svn-src-stabl...@freebsd.org Author: eadler (ports committer) Date: Thu Jan 12 00:02:14 2012 New Revision: 229994 URL: http://svn.freebsd.org/changeset/base/229994 Log: MFC r228445: - Add support for ASCII art splash screens in TheDraw format PR: kern/143370 Approved by: ed Added: stable/9/sys/dev/fb/splash_txt.c - copied unchanged from r228445, head/sys/dev/fb/splash_txt.c stable/9/sys/modules/splash/txt/ - copied from r228445, head/sys/modules/splash/txt/ Modified: stable/9/share/man/man4/splash.4 stable/9/sys/modules/splash/Makefile Directory Properties: stable/9/share/man/ (props changed) stable/9/share/man/man4/ (props changed) stable/9/sys/ (props changed) Modified: stable/9/share/man/man4/splash.4 == --- stable/9/share/man/man4/splash.4 Thu Jan 12 00:01:11 2012 (r229993) +++ stable/9/share/man/man4/splash.4 Thu Jan 12 00:02:14 2012 (r229994) @@ -74,6 +74,14 @@ Bitmaps of other color depths will not b ZSoft PCX decoder. This decoder currently only supports version 5 8-bpp single-plane images. +.It Pa splash_txt.ko +TheDraw binary ASCII drawing file decoder. +Displays a text-mode 80x25 ASCII drawing, such as that produced by +the Binary save format in TheDraw. +This format consists of a sequence +of two byte pairs representing the 80x25 display, where the first byte +is the ASCII character to draw and the second byte indicates the +colors/attributes to use when drawing the character. .El .Pp The @@ -223,6 +231,16 @@ If the VESA support is statically linked necessary to load the VESA module. Just load the bitmap file and the splash decoder module as in the first example above. +.Pp +To load a binary ASCII drawing and display this while booting, include the +following into your +.Pa /boot/loader.conf +: +.Bd -literal -offset indent +splash_txt_load="YES" +bitmap_load="YES" +bitmap_name="/boot/splash.bin" +.Ed .\".Sh DIAGNOSTICS .Sh SEE ALSO .Xr vidcontrol 1 , @@ -256,6 +274,15 @@ module was written by based on the .Pa splash_bmp code. +The +.Pa splash_txt +module was written by +.An Antony Mawer Aq ant...@mawer.org +based on the +.Pa splash_bmp +code, with some additional inspiration from the +.Pa daemon_saver +code. .Sh CAVEATS Both the splash screen and the screen saver work with .Xr syscons 4 Copied: stable/9/sys/dev/fb/splash_txt.c (from r228445, head/sys/dev/fb/splash_txt.c) == --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ stable/9/sys/dev/fb/splash_txt.c Thu Jan 12 00:02:14 2012 (r229994, copy of r228445, head/sys/dev/fb/splash_txt.c) @@ -0,0 +1,135 @@ +/*- + * Copyright (c) 1999 Michael Smith + * Copyright (c) 1999 Kazutaka YOKOTA + * Copyright (c) 2005 Antony Mawer + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * $FreeBSD$ + */ + +#include +#include +#include +#include +#include +#include + +#include + +#include +#include +#include + +static int splash_on = FALSE; + +static int txt_init(video_adapter_t *adp); +static int txt_end(video_adapter_t *adp); +static int txt_splash(video_adapter_t * adp, const in
Re: FLAME - security advisories on the 23rd ? uncool idea is uncool
On Fri, Dec 23, 2011 at 2:06 PM, Lars Engels wrote: > On Fri, Dec 23, 2011 at 06:30:59PM +0100, Bas Smeelen wrote: >> > These vulnerabilities are known many days before in other distributions . >> >> >Thank you very much . >> >> >Mehmet Erol Sanliturk >> >> you're right, these were discussed on the mailinglists also >> _but_ FreeBSD is not a distribution >> It is *a complete operating system* >> Happy holidays > > And the D in BSD is for? ;-) diethylamide ? -- Eitan Adler ___ 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"
Re: SCHED_ULE should not be the default
On Thu, Dec 15, 2011 at 10:32 AM, Steven Hartland wrote: > Lars Engels wrote: >> >> 9.0 ships with gcc and clang which both need to be compiled, 8.2 only >> has gcc. > > > Ahh, any reason we need both, and is it possible to disable clang? man src.conf add WITHOUT_CLANG=yes to /etc/src.conf -- Eitan Adler ___ 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"
Re: SCHED_ULE should not be the default
On Fri, Dec 9, 2011 at 8:15 PM, George Mitchell wrote: > Hope the attached helps. -- George Mitchell You attached dmesg, not a patch. -- Eitan Adler ___ 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"
Re: SCHED_ULE should not be the default
On Fri, Dec 9, 2011 at 6:03 AM, George Mitchell wrote: > dnetc is an open-source program from http://www.distributed.net/. It > tries a brute-force approach to cracking RC4 puzzles and also computes > optimal Golomb rulers. It starts up one process per CPU and runs at > nice 20 and is, for all intents and purposes, 100% compute bound. Try idprio as well (atm it requires root to use though). nice only means "play nice". idprio means "only run when nothing else wants to run". -- Eitan Adler ___ 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"
Re: PAE broken on 7-STABLE
On Tue, Dec 6, 2011 at 12:33 AM, Arnaud Lacombe wrote: > this might be a silly question to ask, but why FreeBSD's VM (or at > least seems to) performs so badly compared to Linux' VM ? Because no one has done the work. :( As much as I hate to say it, we are a volunteer project. That is an excuse, not a reason, but one that has to be addressed nonetheless. -- Eitan Adler ___ 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"
Re: PAE broken on 7-STABLE
On Mon, Dec 5, 2011 at 5:15 PM, Arnaud Lacombe wrote: > Hi, > > A FreeBSD 7-STABLE miserably crashes on the following: Is this also true on 8 and 9 or is the problem unique to 7-STABLE? -- Eitan Adler ___ 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"
Re: linux-f10-flashplugin
On Wed, Sep 28, 2011 at 10:25 AM, S.N.Grigoriev wrote: > All browsers still treat the flash plugin as missing. > What may be wrong? try nspluginwrapper -v -a -u -- Eitan Adler ___ 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"
Re: Authentication tried for XXX with correct key but not from a permitted host
> Maybe it's a bug, but one that has fortuitously useful effects. Bugs are undocumented features. -- Eitan Adler ___ 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"
Re: www/firefox: Firefox 3.6 crashes, Firefox 3.5.7 not
I have no idea if this is related but from pkg-message Firefox 3.6 and HTML5 Certain functions used to display HTML5 elements need the sem module. If your Firefox crashes with the following message while viewing a HTML5 page: "Bad system call (core dumped)" you need to load the sem module (kldload sem). To load sem on every boot put the following into your /boot/loader.conf: sem_load="YES" On Mon, Feb 8, 2010 at 9:04 PM, O. Hartmann wrote: > On 02/08/10 16:20, Gary Jennejohn wrote: > >> On Mon, 08 Feb 2010 13:32:25 + >> "O. Hartmann" wrote: >> >> >> >>> Today, I upgraded Firefox 3.5.7 (built yesterday) to Firefox 3.6. After >>> deleting ~/.mozilla (after I did a buckup, of course), I tried a fresh >>> start of 'firefox3'. After firefox showed up, I realized that no >>> option-field (File, Extras etc) can be used, they are dead and after a >>> few seconds I clicked them, firefox3 is crashing. >>> >>> Since I recompiled firefox 3.5.7 yesterday I was wondering if this is >>> due to some 'false' lib or dependency. Since I figured that I have >>> similar trouble with Thunderbird 3.0.1 after I installed it, I suspect a >>> faulty library causing this behaviour. With Thunderbird 3, I never >>> solved the problem although I tried to rebuild everything with >>> thunderbird via 'portmaster -f'. I'll did this with firefox 3.6 also, >>> but with no success. >>> >>> The crashing is observed on two nearly identical SMP FreeBSD 8.0/amd64 >>> STABLE boxes (make world of today), up-to-date ports. The crash is NOT >>> observed on my private oldish UP box, nearly the same setup, OS at the >>> same revision and ports up to date as of yesterday. Maybe this could be >>> a hint. >>> >>> Any hints or suggestions? >>> >>> >>> >> Try doing "ldd /usr/local/lib/firefox3/firefox-bin" and see if anything >> looks weird. >> >> > I did - and there is nothing weird. > > I checked the installed libraries and they are all rebuild when rebuilding > necessary dependencies for firefox3. > > > You can porbably ignore >> /usr/local/lib/firefox3/firefox-bin: >> libxul.so => not found (0x0) >> libmozjs.so => not found (0x0) >> libxpcom.so => not found (0x0) >> because run-mozilla.sh sets LD_LIBRARY_PATH to include >> /usr/local/lib/firefox3 where these libraries are installed. >> >> I merely deleted my old firefox 3.6 and reinstalled from the port (on >> 9-CURRENT AMD64) and haven't seen any problems. But of course, I've >> been running various incarnations of 3.6 for a while and may have gotten >> all the dependencies already correctly installed. >> >> --- >> Gary Jennejohn >> ___ >> 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" >> >> > > I tried again, left the 'make config'-options as they were set by default, > delete/backuped .mozilla in my home and they restartet firefox3. Nothing > better than previously seen. Try hitting Button 'Tools' at the top menu bar > gives a menu after several seconds, then firefox crashes/core dumps. > > Oliver > > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ 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"
buildworld failure on SSH Makefile
When I do make -DNO_PROFILE buildworld revision 186797 from svn I get ==> secure/usr.bin/ssh-agent (cleandir) rm -f ssh-agent ssh-agent.o ssh-agent.1.gz ssh-agent.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> secure/usr.bin/ssh-keygen (cleandir) rm -f ssh-keygen ssh-keygen.o ssh-keygen.1.gz ssh-keygen.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> secure/usr.bin/ssh-keyscan (cleandir) rm -f ssh-keyscan ssh-keyscan.o ssh-keyscan.1.gz ssh-keyscan.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> secure/usr.sbin (cleandir) ===> secure/usr.sbin/sshd (cleandir) rm -f sshd sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o sshpty.o sshlogin.o servconf.o serverloop.o auth.o auth1.o auth2.o auth-options.o session .o auth-chall.o auth2-chall.o groupaccess.o auth-skey.o auth-bsdauth.o auth2-hos tbased.o auth2-kbdint.o auth2-none.o auth2-passwd.o auth2-pubkey.o monitor_mm.o monitor.o monitor_wrap.o kexdhs.o kexgexs.o auth-krb5.o auth2-gss.o gss-serv.o g ss-serv-krb5.o loginrec.o auth-pam.o auth-shadow.o auth-sia.o md5crypt.o audit.o audit-bsm.o platform.o sftp-server.o sftp-common.o gss-genr.o sshd.8.gz sshd_co nfig.5.gz sshd.8.cat.gz sshd_config.5.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> share (cleandir) "Makefile", line 1: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /home/src/mysrc/local. *** Error code 1 Stop in /home/src/mysrc/local. *** Error code 1 Stop in /home/src/mysrc/local. -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen ___ 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"
