[Bug 225964] Please provide 'reboot -f' Linux equivalent

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225964 Andriy Gapon changed: What|Removed |Added Status|New |Closed

Problem reports for freebsd-bugs@FreeBSD.org that need special attention

2018-02-25 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 222632] connect(2) not available in capability mode

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #21 from Ed Maste --- (In reply to Jan Kokemüller from comment #18) * There's a capsicum-test project where this test could also be added. That said, until or unless we import capsicum-test into FreeBSD or

[Bug 222632] connect(2) not available in capability mode

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #20 from Brooks Davis --- (In reply to Jan Kokemüller from comment #19) This patch did get buried. I've looked it over and it seems correct, but I'm not a capsicum expert. It might help to post to patch

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #12 from fernando.apesteg...@gmail.com --- (In reply to Conrad Meyer from comment #11) OK, this is the new approach: Index: seq.c === --- seq.c (revisión:

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #13 from fernando.apesteg...@gmail.com --- Created attachment 190999 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190999=edit seq output for new approach with cur <= last + (incr / 2) -- You are receiving this

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #10 from fernando.apesteg...@gmail.com --- (In reply to Conrad Meyer from comment #9) Do you mean something like this? Index: seq.c === --- seq.c (revisión:

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #11 from Conrad Meyer --- (In reply to fernando.apesteguia from comment #10) > Do you mean something like this? Oh, sorry, I meant (incr/2) not (step/2). And also for the negative incr case, of course. But

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #14 from Conrad Meyer --- (In reply to fernando.apesteguia from comment #12) > cur >= last - (incr / 2); This one should also be plus. > The problem with this one is that in some cases, we are not stopping

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #15 from Conrad Meyer --- (In reply to Conrad Meyer from comment #14) Hm, no, that's still wrong. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 224529] The talk protocol depends on struct osockaddr which should be kernel-only

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224529 --- Comment #1 from Brooks Davis --- https://reviews.freebsd.org/D14505 contains a fix. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 226212] Not allowed to make system changes in KDE

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226212 Bug ID: 226212 Summary: Not allowed to make system changes in KDE Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 226212] Not allowed to make system changes in KDE

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226212 --- Comment #1 from Slava --- Created attachment 191010 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=191010=edit Can't change KDE wallet configuration -- You are receiving this mail because: You are the

[Bug 226212] Not allowed to make system changes in KDE

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226212 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 142068] [ufs] BSD labels are got deleted spontaneously

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=142068 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 217149] seq(1) inconsistently omits 'last' when using float increment

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org

[Bug 226193] Hacked by Turkish Hacker SpawN #siberordu.biz

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226193 Bug ID: 226193 Summary: Hacked by Turkish Hacker SpawN #siberordu.biz Product: Base System Version: 8.4-STABLE Hardware: Any OS: Any Status: New

[Bug 226193] Hacked by Turkish Hacker SpawN #siberordu.biz

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226193 --- Comment #1 from po...@ugimail.net --- Created attachment 190988 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190988=edit Hacked by Turkish Hacker SpawN #siberordu.biz -- You are receiving this mail because: You are the

seq PR with patch

2018-02-25 Thread Fernando Apesteguía
Hi, Can anyone have a look at this PR? It has a patch and some tests attached to it. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 Thanks. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To

[Bug 226194] make update failure

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226194 Bug ID: 226194 Summary: make update failure Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People

[Bug 224845] Change return type to size_t in dd(1)

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224845 Mark Linimon changed: What|Removed |Added Summary|Change return type to |Change return

vipw PR with patch attached

2018-02-25 Thread Fernando Apesteguía
Hi, Can anyone have a look at this PR? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=40572 It provides a patch that addresses the PR issue. Thanks. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs

find PR fixed long ago

2018-02-25 Thread Fernando Apesteguía
Hi, This PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=67943 was fixed in r246628 and it can be closed. Thanks. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to

[Bug 225964] Please provide 'reboot -f' Linux equivalent

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225964 --- Comment #1 from verma...@interia.pl --- As it turns out this can be achieved with this: # sysctl debug.kdb.panic=1 You may close as resolved. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 67943] find(1) fails when current directory is not readable by user

2018-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=67943 Conrad Meyer changed: What|Removed |Added Resolution|--- |FIXED