Re: ksh ^R vs EDITOR=vi
No idea about ^R, but typing ESC /pattern in vi mode looks for earlier commands containing pattern ... On Sun, Aug 27, 2017 at 05:02:36PM +0200, Jan Stary wrote: > This is current/amd64. I am using ksh(1) as a shell. > Using ^R opens a search in the command history. > However, with 'export EDITOR=vi', pressing ^R > just literarily types '^R' and does not open > the history search. Is that expected? > > Jan -- Martin Bock :wq
Re: locate weirdness
FWIW, on my system it seems to work (and yes, I should upgrade!) $ uname -a OpenBSD foo.bar 4.3 GENERIC.MP#587 i386 On Wed, Jan 11, 2012 at 03:09:50PM -0600, L. V. Lammert wrote: On Wed, 11 Jan 2012, Philip Guenther wrote: Lesson #1: examine the anomalous data for clues. So, you're saying that locate /usr | grep ^/usr | head $ locate /usr | grep '^/usr' | head /usr ... returns nothing but Yep! As does locate /usr locate /home | grep ^/home | head $ locate /home | grep '^/home' | head /home ... returns something? (/home being a stand-in for whatever your unsaid [user file] partition is) Perhaps you should investigate how those two directories differ? That was the original question - both are ffs, both are rw, the only difference between then that /home is nosuid, however that does not affect locate on 3.3, 4.9, or 5.0 (just tested). $ mount /dev/sd0a on / type ffs (local, with quotas) /dev/sd1a on /home type ffs (local, nodev, nosuid, with quotas) /dev/sd2a on /var type ffs (local, nodev, nosuid, with quotas) TFTR! Lee -- Martin Bock :wq
umlauts strangeness in 4.5
timer at 3579545Hz: SpeedStep pciide0 at pci0 dev 31 function 1 Intel 82801CAM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: IC25N030ATCS04-0 wd0: 16-sector PIO, LBA, 28615MB, 58605120 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HITACHI, DVD-ROM GD-S200, 0034 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801CA/CAM SMBus rev 0x01: irq 11 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 128MB SDRAM non-parity PC133CL2 auich0 at pci0 dev 31 function 5 Intel 82801CA/CAM AC97 rev 0x01: irq 11, ICH3 AC97 ac97: codec id 0x43525936 (Cirrus Logic CS4299 rev 6) ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Crystal Semi 3D audio0 at auich0 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask effd netmask effd ttymask mtrr: Pentium Pro MTRR support softraid0 at root root on wd0a swap on wd0b dump on wd0b -- :wq _ Martin Bock (M.Sc.) Theoretical Biology _ __ ___ __ _| |__phone: +49-228-73-2081 University of Bonn | '_ ` _ \ / _` | '_ \ mobile: +49-173-8693707 Kirschallee 1-3 | | | | | | (_| | |_) |_ - - - - - - - - - - - - - - _53115 Bonn |_| |_| |_|\__,_|_.__/ _ - www.theobio.uni-bonn.de - _ Germany
Re: X and Resolution Problems
Hallo! On Fri, Jul 14, 2006 at 02:01:17PM -0700, Darrin Chandler wrote: On Fri, Jul 14, 2006 at 08:36:53PM +, Epkthar Epkthar wrote: After spending a few days reading over forums and continually trying different xorg.conf settings, I havn't managed to gain the resolution 1680x1050 on my Monitor (Phillips 200W). I know from using linux that the resolution is possible using the nv driver, but it won't go above 1280x1024. Setup using X -configure, then inputted the defaultdepth as 24 and under 24 setup the resolutions, have also tried the vesa driver, and also horizontal and vertical settings from my linux setups xorg.conf to no avail. If anyone else has had this problem with X and high resolutions and knows of the solution, or can think of another possible setting i've missed out then please contact me. I also have a stinky nvidious to deal with. Under Linux the X driver was a BLOB from nvidia. Under OpenBSD using generic xorg nv driver I found a modeline calculator and plugged in all the appropriate Here is one: http://www.tkk.fi/Misc/Electronics/faq/vga2rgb/calc.html Bye, Martin numbers. Works fine. I've lost the calculator, but they're not hard to find. Also search the misc@ archives for modeline and you should find a fairly recent discussion with tips, links, etc. -- Darrin Chandler| Phoenix BSD Users Group [EMAIL PROTECTED] | http://bsd.phoenix.az.us/ http://www.stilyagin.com/ | -- :wq .. , , , _ | GS(IT)/MU d-@ a- C++ UB/L++()$ P--- E--- PS+++(+) | /|/| /| /_| | PE(--)+ Y+(++) t++@ 5++ X++ R*(+) b+++ e++@ h* r++ | / | |/-|/__/ `'
