Race VT+X11 on -current

Hi, Sometimes when logging into X11 the keyboard input is not working. Pressing ALT+F9 makes it work. Any idea where the race is? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscr

Re: Race VT+X11 on -current

On Thu, May 7, 2015 at 5:39 AM, Hans Petter Selasky wrote: > Hi, > > Sometimes when logging into X11 the keyboard input is not working. > Pressing ALT+F9 makes it work. Any idea where the race is? > > --HPS > Actually, I have found that switching to ANY other terminal (e.g. ALT-F2) and back to v

Re: Race VT+X11 on -current

> On May 7, 2015, at 09:43, Kevin Oberman wrote: > >> On Thu, May 7, 2015 at 5:39 AM, Hans Petter Selasky wrote: >> >> Hi, >> >> Sometimes when logging into X11 the keyboard input is not working. >> Pressing ALT+F9 makes it work. Any idea where the race is? >> >> --HPS > > Actually, I have

What to do about RCS/OpenRCS

Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot more people than you might think find it useful to have a small version control system for thing l

Re: What to do about RCS/OpenRCS

On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disable GNU RCS and enable the new one I will happily twi

Re: Race VT+X11 on -current

On 05/07/15 20:23, Garrett Cooper wrote: On May 7, 2015, at 09:43, Kevin Oberman wrote: On Thu, May 7, 2015 at 5:39 AM, Hans Petter Selasky wrote: Hi, Sometimes when logging into X11 the keyboard input is not working. Pressing ALT+F9 makes it work. Any idea where the race is? --HPS Act

Re: What to do about RCS/OpenRCS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/07/15 12:09, Pedro Giffuni wrote: > Hello; > > Some of you might recall that right before 10.0-Release there was a > painful attempt to remove GNU RCS from the base system. > > From my point of view, the lessons learned from that were: > > -

Re: What to do about RCS/OpenRCS

Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disabl

Re: Race VT+X11 on -current

On 05/07/15 22:00, Hans Petter Selasky wrote: On 05/07/15 20:23, Garrett Cooper wrote: On May 7, 2015, at 09:43, Kevin Oberman wrote: On Thu, May 7, 2015 at 5:39 AM, Hans Petter Selasky wrote: Hi, Sometimes when logging into X11 the keyboard input is not working. Pressing ALT+F9 makes it

hastd fail and panic on MAXPHYS=1m

Hi all, I have problem with MAXPHYS=1m. (I don't know MAXPHYS=1m works on HAST.) I put "options MAXPHYS=(1024*1024)" in kernel config. Then, update primary node to the kernel and world. If the role back to primary on the machine, writing to the hast device cause an error and panic. I didn't ch

Re: nmount, mountd drops high order MNT_xx flags during a mount update

Doug Rabson wrote: > You could add a single integer-valued vfsopt which holds the > high-order > bits of f_flags? > Yes, that sounds better than any of my ideas. I'll code up a patch and put it up for review unless someone has a better solution. Thanks Doug, rick > On 7 May 2015 at 02:10, Rick M

Re: What to do about RCS/OpenRCS

On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni wrote: > Hello; > > On 05/07/15 14:56, Lyndon Nerenberg wrote: >> >> On Thu, 7 May 2015, Pedro Giffuni wrote: >> >>> Unfortunately I don't use RCS enough (it looks like I should though) so >>> I am not in a good position to take the next step and deal

Re: Race VT+X11 on -current

Hi, I have a fix, attached. I'll just throw this in if nobody objects. Seems like a trivial issue: Prevent switching to NULL or own window in the "vt_proc_window_switch" function. This fixes an issue where X11 keyboard input can appear stuck. The cause of the problem is a duplicate TTY device w

Build failed in Jenkins: FreeBSD_HEAD #2742

See Changes: [adrian] Add initial memory locality cost awareness to the VM, and include a basic ACPI SLIT table parser. For now this just exports the map via sysctl; it'll eventually be useful to userland when there's more useful NUMA s

Re: What to do about RCS/OpenRCS

On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: > > On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni wrote: > > Hello; > > > > On 05/07/15 14:56, Lyndon Nerenberg wrote: > >> > >> On Thu, 7 May 2015, Pedro Giffuni wrote: > >> > >>> Unfortunately I don't use RCS enough (it looks like I s

Re: What to do about RCS/OpenRCS

> Il giorno 08/mag/2015, alle ore 00:26, Doug Brewer ha > scritto: > > On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: > > > > On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni > > wrote: > > > Hello; > > > > > > On 05/07/15 14:56, Lyndon Nerenberg wrote:

Build failed in Jenkins: FreeBSD_HEAD_i386 #98

See Changes: [adrian] Add initial memory locality cost awareness to the VM, and include a basic ACPI SLIT table parser. For now this just exports the map via sysctl; it'll eventually be useful to userland when there's more useful NUM

Re: Build failed in Jenkins: FreeBSD_HEAD_i386 #98

[snip] fixed! -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"