Re: Why does time/ident/daytime/comsat run after an OpenBSD 5.2 install?
frantisek holop's answer is the most logical yet: - hi, i seem to recall reading in some RFC or maybe in one of the stevens books that these services are required for a server. i look at it as being a good internet neighbour, a bit like can you tell me the time please when someone stops you on the street... - p.s.: I created a bounty for this question on the stackexchange site. p.s.2: @Jeremie Courreges-Anglas: are you ok bro'? didn't got your pills? 2013/1/6 Lars Hansson romaby...@gmail.com: ntpd and sshd are only running if you enabled them when installing. For the rest, just turn off inetd. Why are they enabled by default? Search the mailing lists, it has been asked and answered before. Lars
Re: Why does time/ident/daytime/comsat run after an OpenBSD 5.2 install?
As Lars Hansson said, ntpd and sshd are only running if you enabled them when installing. For the rest, just turn off inetd. Like the man said. If you see no use for inetd, don't run it. Why are they enabled by default? Search the mailing lists, it has been asked and answered before. Did you search the mailing lists? In almost all cases, 'search the mailing lists' is a friendly attempt to provide a pointer to good information. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
OSPF over GRE: gre0 address 224.0.0.5: Can't assign requested address
Hi misc@, any ideas why ospfd suddenly stops to work on gre? I see following in /var/log/messages: ospfd[21685]: if_leave_group: error IP_DROP_MEMBERSHIP, interface gre0 address 224.0.0.5: Can't assign requested address hostname.gre0 on disconnected side: tunnel 1.2.3.4 9.8.7.6 description TO_HQ !/sbin/ifconfig gre0 inet 10.10.3.1 10.10.0.3 netmask 255.255.255.255 -inet6 link0 up The only way(seems to be) to fix this is to /etc/rc.d/ospfd stop sh /etc/netstart gre0 /etc/rc.d/ospfd start //mxb
out of swap
This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? Jan OpenBSD 5.2-current (GENERIC.MP) #378: Mon Aug 20 12:55:12 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery real mem = 1054593024 (1005MB) avail mem = 1004150784 (957MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe4410 (25 entries) bios0: vendor Intel Corp. version MOPNV10J.86A.0175.2010.0308.0620 date 03/08/2010 bios0: Intel Corporation D510MO acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT acpi0: wakeup devices SLPB(S4) PS2M(S4) PS2K(S4) UAR1(S4) UAR2(S4) P32_(S4) ILAN(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.97 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu0: 512KB 64b/line 8-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu1: 512KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu2: 512KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu3: 512KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 5 (P32_) acpiprt1 at acpi0: bus 0 (PCI0) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX1) acpiprt4 at acpi0: bus 3 (PEX2) acpiprt5 at acpi0: bus 4 (PEX3) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpicpu2 at acpi0: C1, PSS acpicpu3 at acpi0: C1, PSS acpibtn0 at acpi0: SLPB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 8 int 16 drm0 at inteldrm0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 8 int 16, address 00:27:0e:07:09:9f rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x01: msi pci4 at ppb3 bus 4 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 8 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 8 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 8 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 8 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 8 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe1 pci5 at ppb4 bus 5 pcib0 at pci0 dev 31 function 0 Intel NM10 LPC rev 0x01 ahci0 at pci0 dev 31 function 2 Intel 82801GR AHCI rev 0x01: msi, AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, WDC WD6400BPVT-0, 01.0 SCSI3 0/direct fixed naa.50014ee25979e46a sd0: 610480MB, 512 bytes/sector, 1250263728 sectors sd1 at scsibus0 targ 1 lun 0: ATA, WDC WD10TPVT-00H, 01.0 SCSI3
Re: out of swap
On Mon, Jan 07, 2013 at 01:27:35PM +0100, Jan Stary wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? [snip] UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. -Otto
/var/backups strange behaviour
Hi Before do anything, i read this : man 8 daily I just installed a fresh OpenBSD-5.2 and /var/backups : empty I don't understand why backup is enabled in /var/backups. I explain, if i run the script : 'sh /etc/daily', backups is done. (i.e 'ls /var/backups') In the manpage of daily, it will backup only if : ROOTBACKUP Variable is enable (=1) or altroot partition in /etc/fstab Actually none of these 2 statements are present. Any idea ? Thank you very much. Regards, Wesley
Re: out of swap
On Mon, Jan 07, 2013 at 01:27:35PM +0100, Jan Stary wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking.
Re: /var/backups strange behaviour
On Mon, Jan 07, 2013 at 04:49:12PM +0400, Wesley wrote: Hi Before do anything, i read this : man 8 daily I just installed a fresh OpenBSD-5.2 and /var/backups : empty I don't understand why backup is enabled in /var/backups. I explain, if i run the script : 'sh /etc/daily', backups is done. (i.e 'ls /var/backups') In the manpage of daily, it will backup only if : ROOTBACKUP Variable is enable (=1) or altroot partition in /etc/fstab Actually none of these 2 statements are present. Any idea ? Thank you very much. Regards, Wesley You are confusing things. ROOTBACKUP and config files backups are rtwo different things. Reading docs (and checking references helps): See security(8) (run by daily(8) as documented) and changelist(5) (referred to by security(8)). -Otto
Re: /var/backups strange behaviour
My mistake ! I undestand better. Thank you very much. Cheers, Wesley Le 2013-01-07 17:07, Otto Moerbeek a écrit : On Mon, Jan 07, 2013 at 04:49:12PM +0400, Wesley wrote: Hi Before do anything, i read this : man 8 daily I just installed a fresh OpenBSD-5.2 and /var/backups : empty I don't understand why backup is enabled in /var/backups. I explain, if i run the script : 'sh /etc/daily', backups is done. (i.e 'ls /var/backups') In the manpage of daily, it will backup only if : ROOTBACKUP Variable is enable (=1) or altroot partition in /etc/fstab Actually none of these 2 statements are present. Any idea ? Thank you very much. Regards, Wesley You are confusing things. ROOTBACKUP and config files backups are rtwo different things. Reading docs (and checking references helps): See security(8) (run by daily(8) as documented) and changelist(5) (referred to by security(8)). -Otto
rtorrent is pmrwaiting
Hi, After a recent upgrade to -current (yesterday from ftp.fr.openbsd.org), rtorrent (with ~10 active torrents) ends up waiting on pmrwait (according to top). I cannot even kill -9 this process. I never run into this issue with a one month old -current. OpenBSD 5.2-current (GENERIC) #13: Sat Jan 5 10:57:54 MST 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 259252224 (247MB) avail mem = 244035584 (232MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 01/16/09, BIOS32 rev. 0 @ 0xfa960 apm0 at bios0: Power Management spec V1.2 (slowidle) pcibios0 at bios0: rev 2.1 @ 0xf/0xdfb4 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf40/112 (5 entries) pcibios0: bad IRQ table checksum pcibios0: PCI BIOS has 5 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0xa800 0xef000/0x1000! cpu0 at mainbus0: (uniprocessor) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 vga1 at pci0 dev 1 function 1 AMD Geode LX Video rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 13 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:0d:b9:0d:cd:38 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 glxpcib0 at pci0 dev 15 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 15 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: TS4GCF133 wd0: 1-sector PIO, LBA, 3823MB, 7831152 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) auglx0 at pci0 dev 15 function 3 AMD CS5536 Audio rev 0x01: irq 11, CS5536 AC97 ac97: codec id 0x414c4770 (Avance Logic ALC203 rev 0) ac97: codec features headphone, 20 bit DAC, 18 bit ADC, No 3D Stereo audio0 at auglx0 ohci0 at pci0 dev 15 function 4 AMD CS5536 USB rev 0x02: irq 5, version 1.0, legacy support ehci0 at pci0 dev 15 function 5 AMD CS5536 USB rev 0x02: irq 5 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo 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 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 lm1 at wbsio0 port 0x290/8: W83627HF npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 AMD OHCI root hub rev 1.00/1.00 addr 1 mtrr: K6-family MTRR support (2 registers) umass0 at uhub0 port 4 configuration 1 interface 0 Western Digital My Passport 071A rev 2.00/20.19 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: WD, My Passport 071A, 2019 SCSI2 0/direct fixed sd0: 715377MB, 512 bytes/sector, 1465092096 sectors ses0 at scsibus0 targ 1 lun 1: WD, SES Device, 2019 SCSI2 13/enclosure services fixed ses0: unable to read enclosure configuration vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on wd0a (c917c85befe4920c.a) swap on wd0b dump on wd0b WARNING: / was not properly unmounted -- Manuel Giraud
Re: Strange ksh history behaviour
On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: However, I like vim and as soon as I set the EDITOR env variable to it the arrow up/down functionality is gone. In fact even if EDITOR is set with export EDITOR= the functionality is gone. Commands typed in still appear in the history using fc -l. I just cannot use the arrow-keys. What am I missing here? Can someone confirm this? It's a silly ksh misfeature. ksh switches to vi editing mode as soon as vi is set as an editor. I also prefer emacs editing mode in the shell but use vim, so I put the following line into ~/.kshrc (or ~/.profile if you prefer) to force emacs editing mode in ksh regardless of what EDITOR is set to: set -o emacs
Re: Strange ksh history behaviour
On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: Hello, I just discovered a strange behaviour with ksh-history that I cannot explain. So I hope you can probably help. I read some man pages and used google but didn't find anything useful. If this is is just a RTFM please hit me with it :-) ready ? :-) [...] However, I like vim and as soon as I set the EDITOR env variable to it the arrow up/down functionality is gone. In fact even if EDITOR is set with export EDITOR= the functionality is gone. Commands typed in still appear in the history using fc -l. I just cannot use the arrow-keys. It is the documented behaviour in ksh(1) :-) You could see the EDITOR variable comment in ksh(1): EDITOR If the VISUAL parameter is not set, this parameter controls the command-line editing mode for interactive shells. And as arrow-keys are not used by the 'vi'-like command-line editing... What am I missing here? Can someone confirm this? You need to set your command-line editing mode to emacs. In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR -- Sebastien Marie
Re: Strange ksh history behaviour
Stefan Sperling writes: On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: However, I like vim and as soon as I set the EDITOR env variable to it the arrow up/down functionality is gone. In fact even if EDITOR is set with export EDITOR= the functionality is gone. Commands typed in still appear in the history using fc -l. I just cannot use the arrow-keys. What am I missing here? Can someone confirm this? It's a silly ksh misfeature. ksh switches to vi editing mode as soon as vi is set as an editor. Well, that's one part of the problem. The other issue is that arrow keys don't work in vi mode even though they probably should.
Re: out of swap
This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped?
Re: out of swap
I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? that is for one process.
Re: out of swap
On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? On Jan 07 13:34:10, o...@drijf.net wrote: UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. On Jan 07 14:03:08, es...@nerim.net wrote: 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. This was indeed a build of gtk+3. On Jan 07 07:59:46, amitk...@gmail.com wrote: I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? This was running as root, who is staff: staff:\ :datasize-cur=800M:\ :datasize-max=infinity:\ :maxproc-max=512:\ :maxproc-cur=128:\ :ignorenologin:\ :requirehome@:\ :tc=default:
Re: Strange ksh history behaviour
On 07.01.2013 14:54, Sébastien Marie wrote: In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Thanks a lot. You just solved one of those small problems I've had for years on all my OpenBSD systems. It was a pain in the ass to me at rare intervals. Therefore I was too lazy to read the man page. But now I'm very happy about knowing this solution. :-) .. Bruno Flückiger
Re: Strange ksh history behaviour
On 2013-01-07, Sébastien Marie semarie-open...@latrappe.fr wrote: What am I missing here? Can someone confirm this? You need to set your command-line editing mode to emacs. In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Many programs prefer VISUAL over EDITOR, so this is only of limited help.
Re: out of swap
On Jan 07 15:14:21, h...@stare.cz wrote: On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? On Jan 07 13:34:10, o...@drijf.net wrote: UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. On Jan 07 14:03:08, es...@nerim.net wrote: 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. This was indeed a build of gtk+3. On Jan 07 07:59:46, amitk...@gmail.com wrote: I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? This was running as root, who is staff: No, sorry; root is in the daemon class: daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default:
Re: Strange ksh history behaviour
* Anthony J. Bentley anth...@cathet.us [130107 18:44]: Stefan Sperling writes: On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: However, I like vim and as soon as I set the EDITOR env variable to it the arrow up/down functionality is gone. In fact even if EDITOR is set with export EDITOR= the functionality is gone. Commands typed in still appear in the history using fc -l. I just cannot use the arrow-keys. What am I missing here? Can someone confirm this? It's a silly ksh misfeature. ksh switches to vi editing mode as soon as vi is set as an editor. Well, that's one part of the problem. The other issue is that arrow keys don't work in vi mode even though they probably should. I made a hack (vt220-compatible only) for anyone interested: http://plhk.ru/trash/ksh/0008-ksh-vi-arrow-keys-support.patch More funny diffs at http://plhk.ru/trash/ksh/ -- Alexander Polakov | plhk.ru
Re: Strange ksh history behaviour
Hi, On Mon, Jan 7, 2013 at 2:54 PM, Sébastien Marie semarie-open...@latrappe.fr wrote: It is the documented behaviour in ksh(1) :-) You could see the EDITOR variable comment in ksh(1): Well, what can I say :-) It was late and I was tired or my english is crap and didn't understand... ;-) EDITOR If the VISUAL parameter is not set, this parameter controls the command-line editing mode for interactive shells. And as arrow-keys are not used by the 'vi'-like command-line editing... What am I missing here? Can someone confirm this? You need to set your command-line editing mode to emacs. In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Thanks, a lot for the help. This really solved it. Who would have guessed - one more time where the man pages proved to be right :-D Again, thanks for the help Lars
Re: out of swap
On Mon, Jan 07, 2013 at 03:38:37PM +0100, Jan Stary wrote: On Jan 07 15:14:21, h...@stare.cz wrote: On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. ^^ In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? No, sorry; root is in the daemon class: daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) For starters, you could use the provided snapshots. If you don't, you're supposed to know what you're doing (obviously, there's something missing there). Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. Sad but true...
Re: out of swap
On Jan 07 17:09:16, es...@nerim.net wrote: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) Right. For starters, you could use the provided snapshots. If you don't, I use snapshots and prebuilt packages whenever I can. Compiling this was a workaround - you're supposed to know what you're doing (obviously, there's something missing there). Yesterday's current/amd64, as mirrored at ftp://ftp5.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/ has sets from Jan 5 and x*-sets from Jan 4. I'm not sure if that is the reason, but the obligate pkg_add -ui says Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. I was just confused by the swap messages, which seems to be explained now. Thanks. Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. Time for me to re-read then. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... No doubt. oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. I just didn't know that 1G of RAM that my machine has (laugh away) is not enough for compiling _those_ ports, and that in fact I *will* be hitting (my nonexistent) swap, as Otto explained. Now I do. Thank you.
Re: Strange ksh history behaviour
On Jan 07 14:36:53, s...@spacehopper.org wrote: On 2013-01-07, Sébastien Marie semarie-open...@latrappe.fr wrote: What am I missing here? Can someone confirm this? You need to set your command-line editing mode to emacs. In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Many programs prefer VISUAL over EDITOR, so this is only of limited help. e.g. mutt: EDITOR Specifies the editor to use if VISUAL is unset. VISUAL Specifies the editor to use when composing messages.
Re: out of swap
Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. Right, the rebuilt xenocara (unlike the current x* sets) provides freetype.so.19 and gtk+3 and everything above is happy via pkg_add -ui.
Re: out of swap
Would http://www.openbsd.org/faq/faq14.html#Swap fix your issue? Specifically, section 14.5.3 where you create a swap space and add it to your swap pool? On Mon, Jan 7, 2013 at 10:44 AM, Jan Stary h...@stare.cz wrote: On Jan 07 17:09:16, es...@nerim.net wrote: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) Right. For starters, you could use the provided snapshots. If you don't, I use snapshots and prebuilt packages whenever I can. Compiling this was a workaround - you're supposed to know what you're doing (obviously, there's something missing there). Yesterday's current/amd64, as mirrored at ftp://ftp5.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/ has sets from Jan 5 and x*-sets from Jan 4. I'm not sure if that is the reason, but the obligate pkg_add -ui says Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. I was just confused by the swap messages, which seems to be explained now. Thanks. Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. Time for me to re-read then. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... No doubt. oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. I just didn't know that 1G of RAM that my machine has (laugh away) is not enough for compiling _those_ ports, and that in fact I *will* be hitting (my nonexistent) swap, as Otto explained. Now I do. Thank you.
Re: Kernel Debugging
So now that I got ddb working good I went back and built kernel with KGDB
options per the 'man KGDB' page. I followed the other steps and I have a
null modem cable hooked up. When I run 'gdb bsd.gdb' on the control system
and then 'target remote /dev/cua00', it does not break into debugger on the
target system. Now that current kernel builds with KGDB option, is anyone
using it?
Justin
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Justin Mayes
Sent: Monday, December 24, 2012 11:07 AM
To: Philip Guenther
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
Your right. I can view that struct also. The other structs I tried must have
been out of scope. Thanks for your help Philip.
J
-Original Message-
From: Philip Guenther [mailto:guent...@gmail.com]
Sent: Sunday, December 23, 2012 6:51 PM
To: Justin Mayes
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
On Sun, Dec 23, 2012 at 1:34 PM, Justin Mayes jma...@careered.com wrote:
I was looking into kernel debug options and found that trying to build
a kernel with kgdb option enabled fails.
If no one uses it, it won't keep working. Submitting a patch to fix the
build would be a first step. I suggest trying it both with DDB and without
DDB: those should both work.
Anyone using the kgdb setup? I can
use ddb it's just painful to have to manually walk structures to
examine values. I have moved on to plan B which was to build with
option DDB_STRUCT and the build is a success but the 'show struct'
command always returns 'unknown structure' for anything other than
mbuf. Anyone have any kernel debugging strategies they'd like to share?
DDB_STRUCT works for me for other structures. For example, here's a session
looking at a firefox struct proc:
Stopped at Debugger+0x5: leave
ddb{0} ps/a
PID COMMAND STRUCT PROC * UAREA * VMSPACE/VM_MAP
16253 firefox 0xfe812af09798 0x800032dd6000
0xfe81305ec1d0
8061 xpdf0xfe81280e1a08 0x800032dfe000
0xfe81305ecd30
31009 firefox 0xfe81280e17a0 0x800032df9000
0xfe81305ec1d0
5390 firefox 0xfe81280e1c70 0x800032e0d000
0xfe81305ec1d0
10871 less0xfe81280e1068 0x800032df4000
0xfe81305ece10
28672 vi 0xfe8129b0d7a8 0x800032e16000
0xfe81305ecb70
24081 firefox 0xfe81280e12d0 0x800032def000
0xfe81305ec1d0
29697 firefox 0xfe812af09c68 0x800032de5000
0xfe81305ec1d0
19401 firefox 0xfe812af09a00 0x800032de
0xfe81305ec1d0
27330 firefox 0xfe8135a2b4f0 0x800032ddb000
0xfe81305ec1d0
13735 firefox 0xfe812af09530 0x800032dd1000
0xfe81305ec1d0
819 firefox 0xfe812af092c8 0x800032dcc000
0xfe81305ec1d0
13812 firefox 0xfe812de71c60 0x800032dc2000
0xfe81305ec1d0
15769 firefox 0xfe812af09060 0x800032dc7000
0xfe81305ec1d0
2108 firefox 0xfe812de719f8 0x800032dbd000
0xfe81305ec1d0
7957 firefox 0xfe812de71790 0x800032db8000
0xfe81305ec1d0
20128 firefox 0xfe812de71528 0x800032db3000
0xfe81305ec1d0
4339 firefox 0xfe812de712c0 0x800032da6000
0xfe81305ec1d0
20161 firefox 0xfe812de71058 0x800032da1000
0xfe81305ec1d0
4258 firefox 0xfe812f591c58 0x800032d9c000
0xfe81305ec1d0
4495 firefox 0xfe812f5919f0 0x800032d8f000
0xfe81305ec1d0
ddb{0} show struct
proc 0xfe812af09798
struct proc at 0xfe812af09798 (616 bytes)
p_runq 16
p_list 16
p_p8 fe81368ad7c8
p_thr_link 16
p_fd 8 fe81377d1898
p_vmspace 8 fe81305ec1d0
p_sigacts 8 fe8136f246c0
p_exitsig 40
p_flag 4 4100080
p_spare1 ef
p_stat 13
p_pad1 1 af
p_descfd 1 de
p_pid 4 3f7d
p_hash 16
p_dupfd40
p_thrslpid 82309e1800
p_sigwait 40
p_estcpu 40
p_cpticks 40
p_pctcpu 40
p_wchan8 fe812af09810
p_sleep_to 40
p_wmesg8 8083585c
p_swtime 4 32
p_slptime 4e
p_cpu 8
Re: out of swap
On Jan 07 14:13:15, bra...@gmail.com wrote: Would http://www.openbsd.org/faq/faq14.html#Swap fix your issue? Specifically, section 14.5.3 where you create a swap space and add it to your swap pool? The issue here was my ignorance of the _need_ for more RAM or swap. It's resolved.
Re: Strange ksh history behaviour
On Mon, Jan 07, 2013 at 05:56:00PM +0100, Jan Stary wrote: On Jan 07 14:36:53, s...@spacehopper.org wrote: On 2013-01-07, Sébastien Marie semarie-open...@latrappe.fr wrote: What am I missing here? Can someone confirm this? You need to set your command-line editing mode to emacs. In order to keep EDITOR to vi, you should set VISUAL to emacs in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Many programs prefer VISUAL over EDITOR, so this is only of limited help. e.g. mutt: EDITOR Specifies the editor to use if VISUAL is unset. VISUAL Specifies the editor to use when composing messages. I prefer vim in mutt so I just use: alias mutt='env EDITOR=vim mutt' Since this is on my remote server, I don't need anything else for EDITOR or VISUAL variables. You might or might not be able to use this method. Depends on what you are running that depends on those two variables. Did I mention that I asked earlier on list about same problem? I would search the lists for similar answers. Chris Bennett
Re: Kernel Debugging
I got this. I had 2 com ports on this old target desktop and when I switched
the serial cable to the right one, it worked. I have working DDB kernel with
structs as well as a working kgdb kernel with current.
Justin
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Justin Mayes
Sent: Monday, January 07, 2013 2:35 PM
To: misc@openbsd.org
Subject: Re: Kernel Debugging
So now that I got ddb working good I went back and built kernel with KGDB
options per the 'man KGDB' page. I followed the other steps and I have a
null modem cable hooked up. When I run 'gdb bsd.gdb' on the control system
and then 'target remote /dev/cua00', it does not break into debugger on the
target system. Now that current kernel builds with KGDB option, is anyone
using it?
Justin
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Justin Mayes
Sent: Monday, December 24, 2012 11:07 AM
To: Philip Guenther
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
Your right. I can view that struct also. The other structs I tried must have
been out of scope. Thanks for your help Philip.
J
-Original Message-
From: Philip Guenther [mailto:guent...@gmail.com]
Sent: Sunday, December 23, 2012 6:51 PM
To: Justin Mayes
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
On Sun, Dec 23, 2012 at 1:34 PM, Justin Mayes jma...@careered.com wrote:
I was looking into kernel debug options and found that trying to build
a kernel with kgdb option enabled fails.
If no one uses it, it won't keep working. Submitting a patch to fix the
build would be a first step. I suggest trying it both with DDB and without
DDB: those should both work.
Anyone using the kgdb setup? I can
use ddb it's just painful to have to manually walk structures to
examine values. I have moved on to plan B which was to build with
option DDB_STRUCT and the build is a success but the 'show struct'
command always returns 'unknown structure' for anything other than
mbuf. Anyone have any kernel debugging strategies they'd like to share?
DDB_STRUCT works for me for other structures. For example, here's a session
looking at a firefox struct proc:
Stopped at Debugger+0x5: leave
ddb{0} ps/a
PID COMMAND STRUCT PROC * UAREA * VMSPACE/VM_MAP
16253 firefox 0xfe812af09798 0x800032dd6000
0xfe81305ec1d0
8061 xpdf0xfe81280e1a08 0x800032dfe000
0xfe81305ecd30
31009 firefox 0xfe81280e17a0 0x800032df9000
0xfe81305ec1d0
5390 firefox 0xfe81280e1c70 0x800032e0d000
0xfe81305ec1d0
10871 less0xfe81280e1068 0x800032df4000
0xfe81305ece10
28672 vi 0xfe8129b0d7a8 0x800032e16000
0xfe81305ecb70
24081 firefox 0xfe81280e12d0 0x800032def000
0xfe81305ec1d0
29697 firefox 0xfe812af09c68 0x800032de5000
0xfe81305ec1d0
19401 firefox 0xfe812af09a00 0x800032de
0xfe81305ec1d0
27330 firefox 0xfe8135a2b4f0 0x800032ddb000
0xfe81305ec1d0
13735 firefox 0xfe812af09530 0x800032dd1000
0xfe81305ec1d0
819 firefox 0xfe812af092c8 0x800032dcc000
0xfe81305ec1d0
13812 firefox 0xfe812de71c60 0x800032dc2000
0xfe81305ec1d0
15769 firefox 0xfe812af09060 0x800032dc7000
0xfe81305ec1d0
2108 firefox 0xfe812de719f8 0x800032dbd000
0xfe81305ec1d0
7957 firefox 0xfe812de71790 0x800032db8000
0xfe81305ec1d0
20128 firefox 0xfe812de71528 0x800032db3000
0xfe81305ec1d0
4339 firefox 0xfe812de712c0 0x800032da6000
0xfe81305ec1d0
20161 firefox 0xfe812de71058 0x800032da1000
0xfe81305ec1d0
4258 firefox 0xfe812f591c58 0x800032d9c000
0xfe81305ec1d0
4495 firefox 0xfe812f5919f0 0x800032d8f000
0xfe81305ec1d0
ddb{0} show struct
proc 0xfe812af09798
struct proc at 0xfe812af09798 (616 bytes)
p_runq 16
p_list 16
p_p8 fe81368ad7c8
p_thr_link 16
p_fd 8 fe81377d1898
p_vmspace 8 fe81305ec1d0
p_sigacts 8 fe8136f246c0
p_exitsig 40
p_flag 4 4100080
p_spare1 ef
p_stat 13
p_pad1 1 af
p_descfd 1 de
p_pid 4 3f7d
p_hash 16
p_dupfd40
p_thrslpid 82309e1800
p_sigwait 40
p_estcpu
Re: Tricks for install OpenBSD under Virtualbox, host Windows XP
On 2013-01-06 17:06, Steve Williams wrote: Hi, After recently reading (on this list) about how OpenBSD runs under Virtualbox, I thought I would take it for a test drive on my laptop so I can work in OpenBSD while away on business don't have access to the Internet. My laptop is a Dell Latitude E6500 with a Intel(R) Core(TM)2 Duo CPU (P8600). I have enabled the Virtualization support in the bios. The host system is Windows XP. When I start VirtualBox, I get a dialogue box that says: - VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Certain guests (e.g. OS/2 and QNX) require this feature. Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer. - When I got this message, I disabled the Enable VT-x/AMD-V in the settings of the VM for OpenBSD, but I still get that message. It's a bit confusing. I am trying to install OpenBSD-current (downloaded January 6, 2013). It will get various distances into installing before I get an error. I've even got as far as defining the partitions and the format starting, but it either gives an Illegal Instruction, or a kernel panic. The Intel website indicates it supports VT-x (http://ark.intel.com/products/35569?wapkw=core+2+duo+p8400) It does, but why didn't you try enabling VT-x in the BIOS of your host computer, just like the dialog suggested? Any suggestions/tricks, or am I just out of luck with this combination of hardware/guest OS/OpenBSD? Thanks, Steve -- Hugo Osvaldo Barrera
Re: Tricks for install OpenBSD under Virtualbox, host Windows XP
On 01/08/2013 12:49 AM, Hugo Osvaldo Barrera wrote: On 2013-01-06 17:06, Steve Williams wrote: My laptop is a Dell Latitude E6500 with a Intel(R) Core(TM)2 Duo CPU (P8600). I have enabled the Virtualization support in the bios. It does, but why didn't you try enabling VT-x in the BIOS of your host computer, just like the dialog suggested? Seems like he already tried that.
midi(4) nitpicking
Index: midi.4 === RCS file: /cvs/src/share/man/man4/midi.4,v retrieving revision 1.26 diff -u -p -r1.26 midi.4 --- midi.4 4 Oct 2010 09:32:43 - 1.26 +++ midi.4 8 Jan 2013 02:08:13 - @@ -243,8 +243,7 @@ and later largely rewritten by MIDI hardware was designed for real time performance and software using such hardware must be able to process MIDI events without any noticeable latency (typically no more than 5ms, which -corresponds to the time it takes to the sound to propagate 1.75 -meters). +is the time it takes for sound to propagate 1.75 meters). .Pp The .Ox
Re: Strange ksh history behaviour
On 8 January 2013 03:56, Jan Stary h...@stare.cz wrote: e.g. mutt: EDITOR Specifies the editor to use if VISUAL is unset. VISUAL Specifies the editor to use when composing messages. If in vi mode and have set $VISUAL, it will be used when you press v to edit the commandline in an editor. At least it does on 5.1 with EDITOR=vi and VISUAL=mg (for testing's sake only) Probably best to learn one set of keys and use them in the shell as well. John
Re: Strange ksh history behaviour
I've been using a patch I made months ago. I haven't submitted it to tech@ since I believe people actually want to keep it. I can't post it at the moment because it's just on the CVS checkout and I have other ksh changes that I have to split first.
Re: Tricks for install OpenBSD under Virtualbox, host Windows XP
Hi, I installed Virtualbox 2.2.4 and everything is 100%. It seems the newer version of Virtualbox is confused by my hardware/host os combination and cannot deal with the VT-X, even though it's enabled in my bios. Thanks for all the hints. It took a bit of magical google incantations and reading between the lines to arrive at this solution. Cheers, Steve On 1/6/2013 1:06 PM, Steve Williams wrote: Hi, After recently reading (on this list) about how OpenBSD runs under Virtualbox, I thought I would take it for a test drive on my laptop so I can work in OpenBSD while away on business don't have access to the Internet. My laptop is a Dell Latitude E6500 with a Intel(R) Core(TM)2 Duo CPU (P8600). I have enabled the Virtualization support in the bios. The host system is Windows XP. When I start VirtualBox, I get a dialogue box that says: - VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Certain guests (e.g. OS/2 and QNX) require this feature. Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer. - When I got this message, I disabled the Enable VT-x/AMD-V in the settings of the VM for OpenBSD, but I still get that message. It's a bit confusing. I am trying to install OpenBSD-current (downloaded January 6, 2013). It will get various distances into installing before I get an error. I've even got as far as defining the partitions and the format starting, but it either gives an Illegal Instruction, or a kernel panic. The Intel website indicates it supports VT-x (http://ark.intel.com/products/35569?wapkw=core+2+duo+p8400) Any suggestions/tricks, or am I just out of luck with this combination of hardware/guest OS/OpenBSD? Thanks, Steve
