Re: rpc
Em qua., 20 de mar. de 2024 às 01:44, Geoff Steckel escreveu: > On 3/20/24 00:06, Gustavo Rios wrote: > > Hi folks! > > > > I wonder if nis/nfs/amd a good choice for sharing information and data > > in a heterogeneous environment? > > If not how to replace these technologies > > > > Thanks a lot. > > Gustavo > > NFS/NIS/AMD are very old technology and are not robust. > How to replace NIS ? > Each OS implements different and only somewhat interoperable versions. > > You really need to give a better idea of the size and shape of the problem. > How much data? > What size is each datum? > What latency is allowed? > Concurrency & locking? > What kind of data? > Tightly coupled or looser networked? > Central control or fully distributed? > > It sounds like you want a real-time networked message passing system but > you need to supply vital details. > best, > Geoff Steckel > -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus
openbsd vm with SR-IOV vf nic
Is it very common for people to be running openbsd boxes under virtualization and using an SR-IOV vf nic? I'm curious what cards people are using. It looks like the only available driver is iavf, for the Intel 700 cards? Are there any other drivers I missed? We have some systems with Intel X550 cards in them, based on the 82599 chipset, which openbsd doesn't currently support. Yuichiro NAITO ported a driver from netbsd: https://marc.info/?l=openbsd-tech=168722323125036=2 We tested it under 7.3, and then an updated version for 7.4, and it's been working great. At one point yasuoka@ had said he would review and merge it, but it looks like that hasn't happened yet and I haven't heard back the last couple of times I tried to ask him about it (I assume he's busy with other things and don't want to bug him any more). So I was just wondering if there are any other available drivers I might have missed for other cards we might have, if anybody else was interested in X550/82599 vf support, and if maybe any other dev might be willing to take a look at it and possibly commit it. Thanks much...
wireguard reconfiguration reliability
We're using wireguard to set up VPN connections from various systems deployed on-prem at customer sites to central openbsd boxes to route internal traffic between the remote boxes and the internal network. After a fresh reboot with a given configuration, everything works great. The problem we have is when we later add or remove a remote system and try to reconfigure the wireguard interface on the central servers. Sometimes the new system just won't work, or oddly the new system works fine but an existing system that was working breaks 8-/. When that happens, we generally have to reboot it, at which point everything works. Occasionally ifconfig on the wg interface just wedges completely. When that happens, it won't reboot cleaning, we have to hard reset it. Has anyone else seen this type of behavior? I'm not sure how common it is to have regular ongoing changes to wireguard like we are doing, so it might not pop up often. Thanks much...
rpc
Hi folks! I wonder if nis/nfs/amd a good choice for sharing information and data in a heterogeneous environment? If not how to replace these technologies Thanks a lot. Gustavo -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus
Re: Emacs in console: Meta key problem
Thank you! I confirm that it works without any other configuration. On 3/19/24 17:25, char...@lisp.mobi wrote: init.el: (set-input-mode t nil t) On 3/19/24 03:07, Irek Szcześniak wrote: Hi, I would like to use Emacs in the console, but the problem is the Meta key. I'm using OpenBSD 7.4 GENERIC.MP#1397 amd64 with regular PC keyboards where I got used to the left Alt as the Meta key. I know that instead of using Meta (e.g., Alt+x), I can prefix with Esc, and then press x. However, I would like to get the left Alt work the way I'm used to. But how? Supposedly, this should work: wsconsctl keyboard.encoding=us.metaesc However, it doesn't work for me, and I don't know how to diagnose the problem. I can use Emacs (emacs -nw) in xterm and cwm (from there I can ssh to a different system and can use Emacs with the left Alt key allright), where I had to tweak the .Xdefaults: XTerm*eightBitInput: false XTerm*eightBitOutput: true How to get the console work the way I want? Thanks & best, Irek
Re: Emacs in console: Meta key problem
init.el: (set-input-mode t nil t) On 3/19/24 03:07, Irek Szcześniak wrote: Hi, I would like to use Emacs in the console, but the problem is the Meta key. I'm using OpenBSD 7.4 GENERIC.MP#1397 amd64 with regular PC keyboards where I got used to the left Alt as the Meta key. I know that instead of using Meta (e.g., Alt+x), I can prefix with Esc, and then press x. However, I would like to get the left Alt work the way I'm used to. But how? Supposedly, this should work: wsconsctl keyboard.encoding=us.metaesc However, it doesn't work for me, and I don't know how to diagnose the problem. I can use Emacs (emacs -nw) in xterm and cwm (from there I can ssh to a different system and can use Emacs with the left Alt key allright), where I had to tweak the .Xdefaults: XTerm*eightBitInput: false XTerm*eightBitOutput: true How to get the console work the way I want? Thanks & best, Irek
High Proxmox CPU usage from idle OpenBSD VM
Hi, Idle OpenBSD VM constantly uses ~11% CPU. Linux and FreeBSD VMs with exactly the same configuration use ~1%. What I've tried so far: - removed all network adapters - shutdown all services in OpenBSD VM - changed Machine from default i440fx to q35 - changed CPU types - removed Display - all above in combinations I've posted about this issue on Proxmox forum. https://forum.proxmox.com/threads/high-pve-cpu-usage-from-idle-vm.143550 It would be great if somebody could help me to resolve this. Thank you in advance. pveversion --verbose -- proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve) pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79) proxmox-kernel-helper: 8.1.0 proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1 proxmox-kernel-6.5: 6.5.13-1 proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8 ceph-fuse: 17.2.7-pve2 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx8 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-4 libknet1: 1.28-pve1 libproxmox-acme-perl: 1.5.0 libproxmox-backup-qemu0: 1.4.1 libproxmox-rs-perl: 0.3.3 libpve-access-control: 8.1.2 libpve-apiclient-perl: 3.3.1 libpve-common-perl: 8.1.1 libpve-guest-common-perl: 5.0.6 libpve-http-server-perl: 5.0.5 libpve-network-perl: 0.9.5 libpve-rs-perl: 0.8.8 libpve-storage-perl: 8.1.0 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 5.0.2-4 lxcfs: 5.0.3-pve4 novnc-pve: 1.4.0-3 proxmox-backup-client: 3.1.4-1 proxmox-backup-file-restore: 3.1.4-1 proxmox-kernel-helper: 8.1.0 proxmox-mail-forward: 0.2.3 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.5 proxmox-widget-toolkit: 4.1.4 pve-cluster: 8.0.5 pve-container: 5.0.8 pve-docs: 8.1.4 pve-edk2-firmware: 4.2023.08-4 pve-firewall: 5.0.3 pve-firmware: 3.9-2 pve-ha-manager: 4.0.3 pve-i18n: 3.2.1 pve-qemu-kvm: 8.1.5-3 pve-xtermjs: 5.3.0-3 qemu-server: 8.0.10 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.2-pve2 cat /etc/pve/qemu-server/102.conf - acpi: 1 agent: 0 balloon: 0 bios: ovmf boot: order=scsi0 cores: 1 cpu: host efidisk0: vm:102/vm-102-disk-1.qcow2,efitype=4m,pre-enrolled-keys=1 ,size=528K hostpci0: :01:00.0 hostpci1: :01:00.3 hotplug: 0 ide2: static:iso/OpenBSDinstall74.iso,media=cdrom,size=617966K kvm: 1 localtime: 0 memory: 1024 meta: creation-qemu=8.1.5,ctime=1709128674 name: OpenBSD74 net0: e1000=BC:24:11:32:2C:4A,bridge=vmbr0 numa: 0 ostype: other scsi0: vm:102/vm-102-disk-0.qcow2,iothread=1,size=3G scsihw: virtio-scsi-single serial0: socket smbios1: uuid=21d580fe-69f9-4b33-a508-668f61e0b7b1 sockets: 1 tablet: 0 vmgenid: 2f36d1f6-de51-489b-84fb-fd931aaab966 qm showcmd 102 /usr/bin/kvm -id 102 -name 'OpenBSD74,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server=on ,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket ,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/ 102.pid -daemonize -smbios 'type=1,uuid=21d580fe-69f9-4b33-a508 -668f61e0b7b1' -drive 'if=pflash,unit=0,format=raw,readonly=on ,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.fd' -drive 'if=pflash ,unit=1,id=drive-efidisk0,format=qcow2,file=/dpool/vm/images/102 /vm-102-disk-1.qcow2' -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share /qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/102.vnc ,password=on' -cpu host,+kvm_pv_eoi,+kvm_pv_unhalt -m 1024 -object 'iothread,id=iothread-virtioscsi0' -device 'pci-bridge,id=pci.1 ,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2 ,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.3 ,chassis_nr=3,bus=pci.0,addr=0x5' -device 'vmgenid,guid=2f36d1f6-de51 -489b-84fb-fd931aaab966' -device 'piix3-usb-uhci,id=uhci,bus=pci.0 ,addr=0x1.0x2' -device 'vfio-pci,host=:01:00.0,id=hostpci0 ,bus=pci.0,addr=0x10' -device 'vfio-pci,host=:01:00.3,id=hostpci1 ,bus=pci.0,addr=0x11' -chardev 'socket,id=serial0,path=/var/run /qemu-server/102.serial0,server=on,wait=off' -device 'isa-serial ,chardev=serial0' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2a13b2e23684' -drive 'file= /rpool/static/template/iso/OpenBSDinstall74.iso,if=none,id=drive-ide2 ,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.1,unit=0,drive= drive-ide2,id=ide2' -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3 ,addr=0x1,iothread=iothread-virtioscsi0' -drive 'file=/dpool/vm/images /102/vm-102-disk-0.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none ,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=virtioscsi0.0 ,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server /pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device
Re: Personal Information Notice - Bright Data
I assume those with the proper means to LART these jokers properly will do so. The rest of us are better off ingoring the whole thing. On a somewhat offtopic side note, total number of Mastodon accounts has just broken 15 million, which must be some kind of indicator of going mainstream since I was just notified that two different obvious pr0n spam sources followed my account. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://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.
Re: VPS power consumption
On 3/19/24 08:42, Mizsei Zoltán wrote: Hi, i have installed OBSD on a small KVM based VPS [1]. The VPS dashboard provides knobs to enable/disable the following options (current setting in brackets) - APIC (On) - ACPI (On) As this VPS have a miniscule load I would like to reduce its energy consumption to the minimum and because this I have started to think about the power management. Would it make sense to use obsdfreqd on a VPS? Could you give me any hint to make sure my VPS doesn't consume power unnecessarily? Is there any way to measure or estimate the power usage of a VPS? As you can see, i tried to use virtio based disk and network devices because emulating quirks of hardware may increase power consumption. Thank You! Regards, -- ext In my experience the kernel at idle will take about 5% of a core on the host system. Just keep your system idle and you won't use up more than you should. Let your host system limit your resources, not the other way around. That's just my opinion. Best Regards, -pjp [1] https://extrowerk.com/2024-02-29/Tiny-OpenBSD-VPS.html - Dmesg: OpenBSD 7.4 (GENERIC) #3: Wed Feb 28 06:23:08 MST 2024 r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1056813056 (1007MB) avail mem = 1005203456 (958MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5a20 (9 entries) bios0: vendor SeaBIOS version "1.13.0-2.module_el8.5.0+2608+72063365" date 04/01/2014 bios0: Red Hat KVM acpi0 at bios0: ACPI 1.0 acpi0: sleep states S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: QEMU Virtual CPU version 2.5+, 2600.51 MHz, 06-0d-03 cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,x2APIC,HV,NXE,LONG,LAHF,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 4MB 64b/line 16-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 1000MHz ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) "ACPI0006" at acpi0 not configured acpipci0 at acpi0 PCI0 acpicmos0 at acpi0 "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "QEMU0002" at acpi0 not configured "ACPI0010" at acpi0 not configured acpicpu0 at acpi0: C1(@1 halt!) pvbus0 at mainbus0: KVM pvclock0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9 iic0 at piixpm0 vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio0: address 00:16:3c:xx:xx:xx virtio0: msix shared virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio1 scsibus2 at vioblk0: 1 targets sd0 at scsibus2 targ 0 lun 0: sd0: 20480MB, 512 bytes/sector, 41943040 sectors virtio1: msix per-VQ virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 viomb0 at virtio2 virtio2: apic 0 int 10 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 usb at uhci0 not configured vscsi0 at root scsibus3 at vscsi0: 256 targets softraid0 at root scsibus4 at softraid0: 256 targets sd1 at scsibus4 targ 1 lun 0: sd1: 20479MB, 512 bytes/sector, 41942448 sectors root on sd1a (859d9465c27b589f.a) swap on sd1b dump on sd1b fd0 at fdc0 drive 1: density unknown - $ sysctl hw hw.machine=amd64 hw.model=QEMU Virtual CPU version 2.5+ hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=cd0:,sd0:9db9effb02148826,sd1:859d9465c27b589f,fd0: hw.diskcount=4 hw.sensors.viomb0.raw0=0 (desired) hw.sensors.viomb0.raw1=0 (current) hw.sensors.softraid0.drive0=online (sd1), OK hw.cpuspeed=2600 hw.vendor=Red Hat hw.product=KVM hw.version=RHEL 7.6.0 PC (i440FX + PIIX, 1996)
VPS power consumption
Hi, i have installed OBSD on a small KVM based VPS [1]. The VPS dashboard provides knobs to enable/disable the following options (current setting in brackets) - APIC (On) - ACPI (On) As this VPS have a miniscule load I would like to reduce its energy consumption to the minimum and because this I have started to think about the power management. Would it make sense to use obsdfreqd on a VPS? Could you give me any hint to make sure my VPS doesn't consume power unnecessarily? Is there any way to measure or estimate the power usage of a VPS? As you can see, i tried to use virtio based disk and network devices because emulating quirks of hardware may increase power consumption. Thank You! Regards, -- ext [1] https://extrowerk.com/2024-02-29/Tiny-OpenBSD-VPS.html - Dmesg: OpenBSD 7.4 (GENERIC) #3: Wed Feb 28 06:23:08 MST 2024 r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1056813056 (1007MB) avail mem = 1005203456 (958MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5a20 (9 entries) bios0: vendor SeaBIOS version "1.13.0-2.module_el8.5.0+2608+72063365" date 04/01/2014 bios0: Red Hat KVM acpi0 at bios0: ACPI 1.0 acpi0: sleep states S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: QEMU Virtual CPU version 2.5+, 2600.51 MHz, 06-0d-03 cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,x2APIC,HV,NXE,LONG,LAHF,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 4MB 64b/line 16-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 1000MHz ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) "ACPI0006" at acpi0 not configured acpipci0 at acpi0 PCI0 acpicmos0 at acpi0 "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "QEMU0002" at acpi0 not configured "ACPI0010" at acpi0 not configured acpicpu0 at acpi0: C1(@1 halt!) pvbus0 at mainbus0: KVM pvclock0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9 iic0 at piixpm0 vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio0: address 00:16:3c:xx:xx:xx virtio0: msix shared virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio1 scsibus2 at vioblk0: 1 targets sd0 at scsibus2 targ 0 lun 0: sd0: 20480MB, 512 bytes/sector, 41943040 sectors virtio1: msix per-VQ virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 viomb0 at virtio2 virtio2: apic 0 int 10 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 usb at uhci0 not configured vscsi0 at root scsibus3 at vscsi0: 256 targets softraid0 at root scsibus4 at softraid0: 256 targets sd1 at scsibus4 targ 1 lun 0: sd1: 20479MB, 512 bytes/sector, 41942448 sectors root on sd1a (859d9465c27b589f.a) swap on sd1b dump on sd1b fd0 at fdc0 drive 1: density unknown - $ sysctl hw hw.machine=amd64 hw.model=QEMU Virtual CPU version 2.5+ hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=cd0:,sd0:9db9effb02148826,sd1:859d9465c27b589f,fd0: hw.diskcount=4 hw.sensors.viomb0.raw0=0 (desired) hw.sensors.viomb0.raw1=0 (current) hw.sensors.softraid0.drive0=online (sd1), OK hw.cpuspeed=2600 hw.vendor=Red Hat hw.product=KVM hw.version=RHEL 7.6.0 PC (i440FX + PIIX, 1996) hw.uuid=d0ce8c03-1393-0b4b-99bf-ce5fb8fd6c0e hw.physmem=1056813056 hw.usermem=1056796672 hw.ncpufound=1 hw.allowpowerdown=1 hw.smt=0 hw.ncpuonline=1 hw.power=1 hw.ucomnames=
Emacs in console: Meta key problem
Hi, I would like to use Emacs in the console, but the problem is the Meta key. I'm using OpenBSD 7.4 GENERIC.MP#1397 amd64 with regular PC keyboards where I got used to the left Alt as the Meta key. I know that instead of using Meta (e.g., Alt+x), I can prefix with Esc, and then press x. However, I would like to get the left Alt work the way I'm used to. But how? Supposedly, this should work: wsconsctl keyboard.encoding=us.metaesc However, it doesn't work for me, and I don't know how to diagnose the problem. I can use Emacs (emacs -nw) in xterm and cwm (from there I can ssh to a different system and can use Emacs with the left Alt key allright), where I had to tweak the .Xdefaults: XTerm*eightBitInput: false XTerm*eightBitOutput: true How to get the console work the way I want? Thanks & best, Irek
