Re: buildkernel ULE related breakage

On Thu, Feb 18, 2016 at 2:10 PM, Michal Suszko wrote: > > Hi, > Got this error compiling GENERIC with s/4BSD/ULE/ on recent -CURRENT > ( wrapped long lines ) > > cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes

buildkernel ULE related breakage

Hi, Got this error compiling GENERIC with s/4BSD/ULE/ on recent -CURRENT ( wrapped long lines ) cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I-

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Am Thu, 18 Feb 2016 17:37:52 + Gary Palmer schrieb: > On Thu, Feb 18, 2016 at 06:11:22PM +0100, O. Hartmann wrote: > > Am Thu, 18 Feb 2016 09:29:26 -0700 > > Ian Lepore schrieb: > > > > > On Thu, 2016-02-18 at 16:29 +0100, O. Hartmann wrote: > > >

Re: CVE-2015-7547: critical bug in libc

Hi! > > A short note on the www.freebsd.org website would probably be helpful, > > as this case will produce a lot of noise. > I'd like to second this! This could be some kind of use for the > further propagation of FreeBSD! > Many people asked me since yesterday, whether the operating system I

FreeBSD_HEAD_i386 - Build #2371 - Fixed

FreeBSD_HEAD_i386 - Build #2371 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2371/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2371/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2371/console Change summaries:

Re: Thinkpad T410: resume broken

[snip] Someone should sit me down with pizza and "help" me just modularise the vesa/fb code so we can use it in vt. It isn't /that/ hard, I've just been preoccupied. -a ___ freebsd-current@freebsd.org mailing list

Re: Thinkpad T410: resume broken

On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > > > I've started to observe similar lines in the logs after updating to > > > fresh -CURRENT,

Re: Thinkpad T410: resume broken

On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA > > emulation in the

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On Thu, Feb 18, 2016 at 06:11:22PM +0100, O. Hartmann wrote: > Am Thu, 18 Feb 2016 09:29:26 -0700 > Ian Lepore schrieb: > > > On Thu, 2016-02-18 at 16:29 +0100, O. Hartmann wrote: > > > On Thu, 18 Feb 2016 14:52:44 + > > > RW wrote: > > > > >

Re: CVE-2015-7547: critical bug in libc

Am Wed, 17 Feb 2016 14:50:28 +0100 Kurt Jaeger schrieb: > Hi! > > > The project that's vulnerable is called "glibc", not "libc". The BSDs > > don't use glibc, so the phrase "nothing to see here" applies. glibc > > isn't even available in FreeBSD's ports tree. > > > > TL;DR:

Re: CVE-2015-7547: critical bug in libc

Am Wed, 17 Feb 2016 08:40:03 -0500 Shawn Webb schrieb: > On Wed, Feb 17, 2016 at 02:24:10PM +0100, O. Hartmann wrote: > > It is around now in the media also for non-OS developers: CVE-2015-7547 > > describes a bug in libc which is supposed to affects all Linux

Re: Thinkpad T410: resume broken

On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > > I've started to observe similar lines in the logs after updating to > > fresh -CURRENT, upon resume (on a different laptop though, not T410): > > > > pcib0:

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Am Thu, 18 Feb 2016 11:20:20 -0500 Lowell Gilbert schrieb: > Allan Jude writes: > > > On 2016-02-18 10:29, O. Hartmann wrote: > > >> I'm now down to a small C routine utilizing crypt(3). But this is not what > >> I > >> intend

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Am Thu, 18 Feb 2016 10:54:27 -0500 Allan Jude schrieb: > On 2016-02-18 10:29, O. Hartmann wrote: > > On Thu, 18 Feb 2016 14:52:44 + > > RW wrote: > > > >> On Thu, 18 Feb 2016 14:16:24 +0100 > >> O. Hartmann wrote: > >> > >>> Hello out

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On 2016-02-18 11:29, Ian Lepore wrote: On Thu, 2016-02-18 at 16:29 +0100, O. Hartmann wrote: On Thu, 18 Feb 2016 14:52:44 + RW wrote: On Thu, 18 Feb 2016 14:16:24 +0100 O. Hartmann wrote: Hello out there, I run into a problem and digging for a solution

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Am Thu, 18 Feb 2016 09:29:26 -0700 Ian Lepore schrieb: > On Thu, 2016-02-18 at 16:29 +0100, O. Hartmann wrote: > > On Thu, 18 Feb 2016 14:52:44 + > > RW wrote: > > > > > On Thu, 18 Feb 2016 14:16:24 +0100 > > > O. Hartmann wrote: > > > > >

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Lowell Gilbert wrote on 02/18/2016 17:20: Allan Jude writes: On 2016-02-18 10:29, O. Hartmann wrote: I'm now down to a small C routine utilizing crypt(3). But this is not what I intend to have, since I want to use tools from the FBSD base system. [...] I have

Re: Thinkpad T410: resume broken

On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote: > > > VESA needs to be removed for i915kms, but I've no idea if it needs to be > > > removed for

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On Thu, 2016-02-18 at 16:29 +0100, O. Hartmann wrote: > On Thu, 18 Feb 2016 14:52:44 + > RW wrote: > > > On Thu, 18 Feb 2016 14:16:24 +0100 > > O. Hartmann wrote: > > > > > Hello out there, > > > > > > I run into a problem and digging for a solution didn't work

FreeBSD_HEAD_i386 - Build #2370 - Still Failing

FreeBSD_HEAD_i386 - Build #2370 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2370/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2370/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2370/console Change

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Allan Jude writes: > On 2016-02-18 10:29, O. Hartmann wrote: >> I'm now down to a small C routine utilizing crypt(3). But this is not what I >> intend to have, since I want to use tools from the FBSD base system. >> >> I build images of a small appliance in a secure

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On 2016-02-18 10:29, O. Hartmann wrote: > On Thu, 18 Feb 2016 14:52:44 + > RW wrote: > >> On Thu, 18 Feb 2016 14:16:24 +0100 >> O. Hartmann wrote: >> >>> Hello out there, >>> >>> I run into a problem and digging for a solution didn't work out. >>> >>> Problem: I

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On Thu, 18 Feb 2016 14:52:44 + RW wrote: > On Thu, 18 Feb 2016 14:16:24 +0100 > O. Hartmann wrote: > > > Hello out there, > > > > I run into a problem and digging for a solution didn't work out. > > > > Problem: I need a string that reflects the hashed password

Re: Thinkpad T410: resume broken

On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote: > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote: > > Looking through dmesg, it seems that other USB devices (build-in) are > > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after > > resume, just not the

Re: Memory modified after free in "MAP ENTRY" zone (vm_map_entry_t->read_ahead)

On Mon, Feb 15, 2016 at 11:07:11AM +0200, Andriy Gapon wrote: > On 15/02/2016 00:27, Alan Cox wrote: > > > > On Sun, Feb 14, 2016 at 8:09 AM, Andriy Gapon > > wrote: > > > > On 10/02/2016 23:28, Andriy Gapon wrote: > > > > > > Over a span

Re: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

On Thu, 18 Feb 2016 14:16:24 +0100 O. Hartmann wrote: > Hello out there, > > I run into a problem and digging for a solution didn't work out. > > Problem: I need a string that reflects the hashed password for the > usage with > > passwd -H 0 Did you mean -h? > I think the procedure is using

Re: Thinkpad T410: resume broken

On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote: > > VESA needs to be removed for i915kms, but I've no idea if it needs to be > > removed for Nvidia. The video reset code was reworked in 10 so that > > having VESA

Re: Thinkpad T410: resume broken

On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote: > > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote: > > > Looking through dmesg, it seems that other USB devices (build-in) are > > > reappearing

Re: CVE-2015-7547: critical bug in libc

On Thu, 18 Feb 2016, Joe Holden wrote: On 17/02/2016 14:07, Daniel Kalchev wrote: On 17.02.2016 ?., at 15:40, Shawn Webb wrote: TL;DR: FreeBSD is not affected by CVE-2015-7547. Unless you use Linux applications under emulation. Daniel Which is supported by

FreeBSD_HEAD_i386 - Build #2369 - Failure

FreeBSD_HEAD_i386 - Build #2369 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2369/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2369/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2369/console Change summaries:

Re: CVE-2015-7547: critical bug in libc

On 17/02/2016 14:07, Daniel Kalchev wrote: On 17.02.2016 г., at 15:40, Shawn Webb wrote: TL;DR: FreeBSD is not affected by CVE-2015-7547. Unless you use Linux applications under emulation. Daniel Which is supported by ports so at most it should be a ports

HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?

Hello out there, I run into a problem and digging for a solution didn't work out. Problem: I need a string that reflects the hashed password for the usage with passwd -H 0 I think the procedure is using sha512 -s Password and using this output for further processing, but how? I looked for

Unable to kldload vesa.ko (but works from loader.conf)

Hi there, I've decided to give -CURRENT a try on my i386 laptop with a 915GM video (supported by i915kms.ko) @ r295286; minimal kernel with most of the stuff loaded from /boot/loader.conf. While debugging suspend/resume issues, I've found out that loading vesa.ko now apparently only works from