FYI:
https://svnweb.freebsd.org/changeset/base/312551
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FYI:
https://svnweb.freebsd.org/changeset/base/312551
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
A 2014 change broke the umask handling in /etc/rc.d/random,
leaving /entropy with ug+r permissions. Quick fix attached,
mirroring random_stop() behavior.
(Incidentally, /usr/libexec/save-entropy is still fine for
/var/db/entropy/*, as is /etc/rc.d/random for the new
/boot/entropy.)
--- /etc/rc
hiya,
Mechanically it doesn't look /that/ hard:
* vesa.ko pulls in the vesa.c bits and the syscons vesa control bits.
Ideally we'd have them as two separate modules, so you could load
"vesa" without needing the syscons bits.
* Maybe then write a vt 'fb' interface to talk to the old-school
framebu
On Fri, Jan 20, 2017 at 09:46:37AM -0800, Pete Wright wrote:
> >
>
> Hey there - can you paste the error you are getting? I've never tried
> building the drm-next branch inside a jail, but maybe your trace will help
> debug it.
>
The steps to reproduce were right in the first message:
> > m
On 1/20/17 6:06 AM, Christian Schwarz wrote:
I am trying to build drm-next-4.7 from the FreeBSDDesktop
repository [1] for use as a poudriere jail.
However, libstd++ is missing in the installation generated with the
following commands:
make buildworld ...
make installworld DESTDIR=/path/to
On 20/01/2017 02:09, Larry Rosenman wrote:
> Thu Jan 19 18:03:38 CST 2017
>
> FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997: Sat Jan
> 14 22:35:29 CST 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER
> amd64
>
> panic: racct_adjust_resource: resource 4 usage < 0
I am trying to build drm-next-4.7 from the FreeBSDDesktop
repository [1] for use as a poudriere jail.
However, libstd++ is missing in the installation generated with the
following commands:
make buildworld ...
make installworld DESTDIR=/path/to/jail/dir
make distribution DESTDIR=/path/to/ja
El d�a Friday, January 20, 2017 a las 09:39:06AM +0100, Andreas Nilsson
escribi�:
> Good good. I am in no way opposed to the "infrastructure" change of
> separating the targets, sounds like a bit of makefile-fun actually. And
> having tools to create memsticks from ones preferred environment woul
On Thu, Jan 19, 2017 at 8:58 PM, Glen Barber wrote:
> On Thu, Jan 19, 2017 at 08:50:34PM +0100, Andreas Nilsson wrote:
> > On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber wrote:
> > > I do want to weigh in here and inform I am actively watching this
> > > thread. clang(1) is not in disc1.iso or bo
10 matches
Mail list logo