Re: CFT: EVDEV support in psm(4) driver

Hi, On 08.06.2017 01:32, Anthony Jenkins wrote: > I'm seeing flakiness in X11 (KDE) with evdev enabled - a couple keys are > reporting multiple (wrong) events and some aren't emitting any events > (or they are, but they're NoSymbol): It is true that the Evdev drivers emit other keycodes compared

Re: CFT: EVDEV support in psm(4) driver

I'm seeing flakiness in X11 (KDE) with evdev enabled - a couple keys are reporting multiple (wrong) events and some aren't emitting any events (or they are, but they're NoSymbol): - Down arrow: emits KeyPress for keycode 116 (Super_R), KeyRelease for keycode 116, KeyRelease for keycode 104

Call for 2017Q2 Quarterly Status Reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 7, 2017, for work done in April through June. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to

Re: mount_smbfs gives error when stored crypted pw is used

On Wed, Jun 7, 2017, at 12:29 PM, O. Hartmann wrote: > Am Wed, 7 Jun 2017 19:22:34 +0200 > Matthias Apitz schrieb: > > > El día miércoles, junio 07, 2017 a las 02:35:31p. m. +0200, Matthias Apitz > > escribió: > > > > > I have located the bug in

Re: nvidia drivers mutex lock

I was just looking through dmesg and noticed these: Jun 6 21:40:52 blubee kernel: nvidia-modeset: Allocated GPU:0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI::01:00.0 Jun 6 21:41:05 blubee kernel: NVRM: GPU at PCI::01:00: GPU-54a7b304-c99d-efee-0117-0ce119063cd6 Jun 6 21:41:05

Re: mount_smbfs gives error when stored crypted pw is used

Am Wed, 7 Jun 2017 19:22:34 +0200 Matthias Apitz schrieb: > El día miércoles, junio 07, 2017 a las 02:35:31p. m. +0200, Matthias Apitz > escribió: > > > I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c > > > > The printf(3C) calls have been added for

Re: mount_smbfs gives error when stored crypted pw is used

El día miércoles, junio 07, 2017 a las 02:35:31p. m. +0200, Matthias Apitz escribió: > I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c > > The printf(3C) calls have been added for debugging; the bug is the > addition of 13 after crypting every char which let the mask used in ^

Re: mount_smbfs gives error when stored crypted pw is used

I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c The printf(3C) calls have been added for debugging; the bug is the addition of 13 after crypting every char which let the mask used in ^ operation exceeding 256, i.e. more than one byte, if the string to be crypted is long enough.

Re: [libltdl] removal from gnu ports

On Wed, Jun 07, 2017 at 11:33:32AM +0100, David Chisnall wrote: > On 7 Jun 2017, at 10:33, blubee blubeeme wrote: > > > > Hi > > > > I'm sure I was reading yesterday on a different machine about the linker > > flag -ld which has something to do with gnu dlopen and how it's

Re: [libltdl] removal from gnu ports

On 7 Jun 2017, at 10:33, blubee blubeeme wrote: > > Hi > > I'm sure I was reading yesterday on a different machine about the linker > flag -ld which has something to do with gnu dlopen and how it's ok to > remove those from your Makefile since FreeBSD handles dlopen and a

[libltdl] removal from gnu ports

Hi I'm sure I was reading yesterday on a different machine about the linker flag -ld which has something to do with gnu dlopen and how it's ok to remove those from your Makefile since FreeBSD handles dlopen and a few other things from that header in the standard libc. Is that correct? I'm

Re: [sed] command failure? Porting a project to FreeBSD

Am 07.06.17 um 11:06 schrieb Jov: > I don't think there is. > Man page of FreeBSD tool may have a section of STANDARDS and/or > COMPATIBILITY, but it does not list all the difference with GNU version. Greg Leheys 'Porting Unix Software' published by O'Reilly and later re-released under Creative

Re: [sed] command failure? Porting a project to FreeBSD

I don't think there is. Man page of FreeBSD tool may have a section of STANDARDS and/or COMPATIBILITY, but it does not list all the difference with GNU version. 2017-06-07 15:40 GMT+08:00 blubee blubeeme : > Ahhh, that was it. Doing a find and ask to replace all instances

Re: [sed] command failure? Porting a project to FreeBSD

On 07/06/2017 09:40, blubee blubeeme wrote: > Ahhh, that was it. Doing a find and ask to replace all instances of sed > with gsed passed that part. > > By the way, is knowledge like this written down somewhere centralized or is > it just floating in the ether? >From my experience of porting

Re: [sed] command failure? Porting a project to FreeBSD

Ahhh, that was it. Doing a find and ask to replace all instances of sed with gsed passed that part. By the way, is knowledge like this written down somewhere centralized or is it just floating in the ether? Thank you, Owen On Wed, Jun 7, 2017, 14:26 Jov wrote: > The default

undefined reference to `em_intr'

Hi, since two or three weeks I'm unable to build the -CURRENT kernel due to undefined references to `em_intr`. The build commandline is `make -j2 KERNCONF=GENERIC-NODEBUG buildkernel`. Due to the ino64-change, I've cleared /usr/obj to rebuild everything. Also, I'm using meta-mode. The error-log,

Re: [sed] command failure? Porting a project to FreeBSD

The default sed on FreeBSD is different from GNU sed,there is some limit for bsd sed.You can try to patch the makefile to using gsed. 2017-06-07 14:10 GMT+08:00 blubee blubeeme : > Hello > > I am trying to bring these updated print drivers to FreeBSD: >

[sed] command failure? Porting a project to FreeBSD

Hello I am trying to bring these updated print drivers to FreeBSD: https://github.com/utsushi/utsushi.git There's the automake scripts in there that's sorta helpful but I seem to have gotten stuck with something. I made sure that my environmental variables are set LDFLAGS -L/usr/local/lib