https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195929
Pedro F. Giffuni changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|p...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195929
Pedro F. Giffuni changed:
What|Removed |Added
Flags||mfc-stable9-,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195929
--- Comment #36 from commit-h...@freebsd.org ---
A commit references this bug:
Author: pfg
Date: Tue Jul 19 22:56:41 UTC 2016
New revision: 303047
URL: https://svnweb.freebsd.org/changeset/base/303047
Log:
sed(1): Assorted cleanups
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211235
Bug ID: 211235
Summary: /etc/portsnap.conf has INDEX.11 while we are now at 12
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211186
--- Comment #8 from Steven Hartland ---
Does the machine support EFI? If so have you tried an EFI install?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203376
Bug 203376 depends on bug 210382, which changed state.
Bug 210382 Summary: Remove hardcoded maximum size (2048x1600) from vt(4)
framebuffer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210382
What|Removed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210382
Conrad E. Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210382
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Tue Jul 19 19:20:48 UTC 2016
New revision: 303043
URL: https://svnweb.freebsd.org/changeset/base/303043
Log:
Increase vt(4) framebuffer maxi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210382
Conrad E. Meyer changed:
What|Removed |Added
Blocks|202288 |
Referenced Bugs:
https://bugs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211186
--- Comment #7 from Andriy Gapon ---
Just an observation that error 49 (0x31 aka 31h) seems to mean "no media in
drive":
http://www.ctyme.com/intr/rb-0606.htm#Table234
So it could be a benign error from ZFS probing of the card reader, but i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211186
--- Comment #6 from Dan MacDonald ---
Created attachment 172730
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172730&action=edit
error trying to boot 10.3 amd64 in a mirrored ZFS config
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211186
--- Comment #5 from Dan MacDonald ---
I've tried installing FreeBSD-10.3-RELEASE-amd64-memstick.img on the same
machine in a mirrored ZFS config now but I'm getting the same or very similar
error - see the attached screenshot. The differenc
View this email in your web browser
http://etrack.michigangrantsfunding.com/campaigns/sc104x50ln97d/web-version/aq398hvg2p919
THE INSIDER'S GUIDE TO GRANTS IN MICHIGAN: How to find thousands of
Michigan's 'hidden' foundations
Hello,
In theory, "getting grants" is a great opportunity that
non
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211224
--- Comment #2 from Larry Rosenman ---
As an additional note, re-running the build with -DNO_CLEAN gets past this, so
I don't know if my old(ish) hw has an issue.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211225
Bug ID: 211225
Summary: [PATCH]: CRASH: telnetd crashes periodically
Product: Base System
Version: 10.3-STABLE
Hardware: Any
OS: Any
Status: New
Key
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211224
Bug ID: 211224
Summary: clang compile/core dump
Product: Base System
Version: 11.0-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only M
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211224
--- Comment #1 from Larry Rosenman ---
I can provide the cpp file as well
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211195
--- Comment #2 from eniorm ---
Thats correct. I saw now and understood.
How can -r flag to remove home if users has no home dir :D
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219
--- Comment #1 from Alexey ---
This commands turn status to "no carrier" after disconnecting cable:
ifconfig em0 down & ifconfig em0 up
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219
Bug ID: 211219
Summary: NIC status does not pass into a state of "no carrier"
after disconnecting the cable.
Product: Base System
Version: 10.3-RELEASE
Hardware: i386
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211213
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205690
Vladimir Kondratyev changed:
What|Removed |Added
Attachment #172681|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211186
--- Comment #4 from Dan MacDonald ---
Hi Steven
Yes, my HDs are configured as the first two boot devices in the BIOS.
My BIOS doesn't have any RAID features. I can basically enable/disable
individual ports, choose the SATA gen (1,2 or 3)
23 matches
Mail list logo