https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211355
Bug ID: 211355
Summary: libfetch is vulnerable to httpoxy
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185603
Pedro F. Giffuni changed:
What|Removed |Added
Component|gnu |bin
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209368
Pedro F. Giffuni changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211354
Bug ID: 211354
Summary: freebsd-update cannot update 11.0-BETA2
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204748
Ed Maste changed:
What|Removed |Added
Flags||mfc-stable11?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #33 from Peter Wemm ---
With the patch from #30 the machine in question hasn't had any more hiccups. It
is behaving in a bug-compatible way with the way it was before the commit that
started the panics.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204748
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: emaste
Date: Mon Jul 25 00:49:27 UTC 2016
New revision: 303282
URL: https://svnweb.freebsd.org/changeset/base/303282
Log:
avoid building otusfw when
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537
Pedro F. Giffuni changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191304
Pedro F. Giffuni changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537
--- Comment #1 from Pedro F. Giffuni ---
Created attachment 172959
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172959=edit
cron-mime patch (downloaded JIC it disappears some day)
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204504
Pedro F. Giffuni changed:
What|Removed |Added
Attachment #163060|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208661
Pedro F. Giffuni changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204650
Pedro F. Giffuni changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194466
Pedro F. Giffuni changed:
What|Removed |Added
Summary|Update printf(1) to support |[patch]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192971
Pedro F. Giffuni changed:
What|Removed |Added
Attachment #146248|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #32 from Peter Wemm ---
It fairly consistently prints one or two 'GEOM new disk .. 0 bytes' before the
disk probe messages but has not crashed. It is usually different disks each
time. And it has not ever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #31 from Peter Wemm ---
The first few boot attempts looked like this:
...
(da0:mpt0:0:0:0): UNMAPPED
(da1:mpt0:0:1:0): da0 at mpt0 bus 0 scbus0 target 0 lun 0
da0: Fixed Direct Access SCSI-3 device
da0:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211333
Jilles Tjoelker changed:
What|Removed |Added
Status|New |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211333
Bug ID: 211333
Summary: Inconsistent exposure of unlinkat and AT_REMOVEDIR
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #30 from Andrey V. Elsukov ---
Created attachment 172924
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172924=edit
Increase debugging in geom_disk
Can you apply this patch and enable bootverbose
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #29 from Andrey V. Elsukov ---
(In reply to Peter Wemm from comment #28)
> There is no size change. The problem is that instead of copying the media
> size, you're introducing a new resize event at open time
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #28 from Peter Wemm ---
There's no size decreases. The sizes match what is in the initial probe
messages.
What's happening is that the disk is mis-partitioned like this:
Disk size: 143374650 sectors
sector
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #27 from Andrey V. Elsukov ---
(In reply to Peter Wemm from comment #26)
> On closer examination, the GPT headers on these drives have strange things
> going on. It does look like there's a 6 sector
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211195
--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bapt
Date: Sun Jul 24 08:21:21 UTC 2016
New revision: 303257
URL: https://svnweb.freebsd.org/changeset/base/303257
Log:
Do not try to delete the home
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211195
--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bapt
Date: Sun Jul 24 08:12:23 UTC 2016
New revision: 303256
URL: https://svnweb.freebsd.org/changeset/base/303256
Log:
iDo not try to delete the home
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201953
--- Comment #2 from Robert Watson ---
Just to cross reference the two sets of bug reports:
https://github.com/openbsm/openbsm/issues/3
https://github.com/openbsm/openbsm/issues/2
Filed by brueffer.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #26 from Peter Wemm ---
On closer examination, the GPT headers on these drives have strange things
going on. It does look like there's a 6 sector overallocation:
GEOM_PART: da1 was automatically resized.
27 matches
Mail list logo