Search results

X fails to come up when I configure it thus in /etc/X11/xorg.conf: Section "Files" FontPath "/usr/local/lib/X11/fonts/dejavu/" EndSection Section "Module" Load "freetype" EndSection Section "Device" Identifier "Card0" Driver "Intel" # BusID "PCI:0:2:0" EndSection What should I be...

This is actually a quite useful workaround for the lack of arrays in the Bourne shell. Consider the following method of passing through two parallel lists more than once. Disclaimer: I haven't actually run the code that I'm typing here, but I've run code quite like it. Note that it comes...

Seeing as the size for the linux module is listed as 43c7c, that has to be hex. And it's probably in bytes; translated to decimal, it's 277628, and the size of linux.ko is 692872. (All this is for 10.2-RELEASE).

If, to keep my scripts simple, I load a module that I might not use, and I end up not using it until I reboot the machine later, what has the unnecessary module loading cost me? I'm thinking of the linux module, but I don't that that's relevant.

On a lark, I compared the rgb.txt in 10.2-RELEASE with that provided by Debian 7 ("wheezy"). The Debian one provided one color that FreeBSD did not: 215 7 81 DebianRed The FreeBSD one provided 30 colors that FreeBSD did not. Does anyone know who Rebecca is, and how she got a color named...

On page 308 of Valerie Quercia and Tim O'Reilly's X Window Systerm User's Guide (1993), volume 3 of the excellent X Window books pubished by O'Reilly, one finds: The rgb.txt file, usually located in /usr/lib/X11, is supplied with the standard distribution of X and consists of predefined color...

Fortunately, all I have to deal with is the keyboard on virtual consoles. No mouse, no relevant network activity, no ppp. The only program to use ptys would be one that I would write, to keep track of keyboard activity on each virtual console. So it would be as innocent as I would want to make...

Bingo. In this case, all relevant activity is local. The only goal is to prevent the local screen from disappearing out from under a keyboarding guy for the purpose of showing the alarm screen.

Sounds good! Which of these is the keyboard? (And where would I go to find the answer to that myself?) home:~$ vmstat -i interrupt total rate irq18: ehci0 uhci5 4 0 irq19: uhci2 uhci4* 90585 4 irq21: uhci1 11481 0 cpu0:timer 446896 23 irq256: em0 33758 1 irq257: hdac0 92 0...

Bingo. Off the shelf, 10.2-RELEASE provides a /usr/bin/lesspipe.sh that runs fast and is so breathtakingly simple that I can quote it here in its entirety without even needing to catch my breath: #! /bin/sh # ex:ts=8 # $FreeBSD: releng/10.2/usr.bin/less/lesspipe.sh 207842 2010-05-10 06:59:50Z...

I can't find any differences between the two environments. But if I unset LESSOPEN, the problem goes away. I'm continuing to investigate.

This might seem a question about less, but I don't think it is. I have two systems with basically the same hardware, one running Linux and one running 10.2-RELEASE. On each, I run less on a half-megabyte text file. On FreeBSD, it takes almost a minute for data to show on the screen. On...

This provides a method for a sort of manual kludge, and is intriguing. What I was hoping for was something that didn't require extra manual effort at the time of keyboard entry. The only way I can think of to do this automatically is for each VT to feed everything from the keyboard to a pty...

What I'm looking for is to avoid switching virtual terminals if there has been typing on any virtual terminal within the most recent few seconds.

If I'm running a FreeBSD system without X, but with several virtual terminals doing various things, under certain circumstances I will use vidcontrol() to switch to a particular virtual terminal in case of an alarm event. But I don't want to do that if I'm actively typing in one or another...

Aye, that's my problem. :(

I wish that would have worked for me. :(

I have edited the title to remove the "SOLVED". I've proposed a workaround, but I'd really like to know whether there's a way to restrict the screen to 80x25 without messing with font size.

I've found a workaround. I still use kern.vty=vt, of course, but none of the rest of it. Remember that the font I was using was vgarom-8x16. What I did was to create a new font, slightly taller than vgarom-8x16. One new font is all I needed, but I created several, in the spirit of...

The trick is to get into X, move to a virtual console, and still expect to see exactly 25 lines on the screen. I tried all seven combinations of at least one of: specifying font vgarom-8x16; setting hw.vga.textmode=1; and setting kern.vt.fb.default_mode="640x480". (And yes, I didn't forget the...