Re: Installer doesn't see sd0 on qemu guest 6.5-current
As you can see in dmesg, it actually sees sd0, and it does not detach. Instead, the device node just isn't in /dev, because the insaller does create that on the fly. Since you are not using the installer, you have to manually type cd /dev && sh MAKEDEV sd0 On Sat, Jun 01, 2019 at 09:08:58PM +0300, Maksym Sheremet wrote: > There is a 6.5-current VM running with QEMU on linux host. Usually the > VM is being updated to the latest snapshot once per 10 days. Everything > was OK with with 2019-04-21 snapshot. The problem has been appeared > since 2019-05-01 snapshot. > > The VM is installed on a dedicated drive with FDE. It is detected as sd0 > by bsd.rd booted from install65.iso. But once installer is started the > drive disappears. Here is full output: > > >> OpenBSD/amd64 CDBOOT 3.43 > boot> > cannot open cd0a:/etc/random.seed: No such file or directory > booting cd0a:/6.5/amd64/bsd.rd: 3691345+1532928+3889096+0+598016 > [373454+128+451752+300829]=0xa58318 > entry point at 0x81001000 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2019 OpenBSD. All rights reserved. > https://www.OpenBSD.org > > OpenBSD 6.5-current (RAMDISK_CD) #50: Fri May 31 20:22:49 MDT 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 2130558976 (2031MB) > avail mem = 2062069760 (1966MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5b10 (9 entries) > bios0: vendor SeaBIOS version "1.12.0-20181126_142135-anatol" > date 04/01/2014 > bios0: QEMU Standard PC (i440FX + PIIX, 1996) > acpi0 at bios0: rev 0 > acpi0: tables DSDT FACP APIC > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: QEMU Virtual CPU version 2.5+, 2295.00 MHz, 06-06-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: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: apic clock running at 1000MHz > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins > acpiprt0 at acpi0: bus 0 (PCI0) > acpicpu at acpi0 not configured > "ACPI0006" at acpi0 not configured > "PNP0A03" at acpi0 not configured > 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 > pvbus0 at mainbus0: KVM > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 > "Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured > 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) > pciide0: channel 1 disabled (no drives) > uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 > int 11 > "Intel 82371AB Power" rev 0x03 at pci0 dev 1 function 3 not configured > vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02 > vga1: aperture needed > wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 > vio0 at virtio0: address 08:00:27:77:c1:d5 > virtio0: msix shared > virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00 > vioblk0 at virtio1 > scsibus0 at vioblk0: 2 targets > sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct > fixed > sd0: 114473MB, 512 bytes/sector, 234441632 sectors > virtio1: msix shared > virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory Balloon" rev > 0x00 > virtio2: no matching child driver; not configured > ahci0 at pci0 dev 7 function 0 "Intel 82801I AHCI" rev 0x02: apic 0 > int 11, AHCI 1.0 > ahci0: port 0: 1.5Gb/s > scsibus1 at ahci0: 32 targets > cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom > removable > usb0 at uhci0: USB revision 1.0 > uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev > 1.00/1.00 addr 1 > isa0 at mainbus0 > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > com0: console > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > pckbd0 at pckbc0 (kbd slot) > wskbd0 at pckbd0: console keyboard, using wsdisplay1 > softraid0 at root > scsibus2 at softraid0: 256 targets > root on rd0a swap on rd0b dump on rd0b > erase ^?, werase ^W, kill ^U, intr ^C, status ^T > > Welcome to the OpenBSD/amd64 6.5 installation program. > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s > # bioctl -c C -l /dev/sd0a softraid0 > bioctl: could not open /dev/sd0a: No such file or directory > # ls /dev > MAKEDEV cua01 klogrcd0c rrd0c rwd0g rwd0o ttyC0 wd0gwd0o > bio diskmap kmemrd0arst0rwd0h rwd0p urandom wd0hwd0p > bpf enrst0
Installer doesn't see sd0 on qemu guest 6.5-current
There is a 6.5-current VM running with QEMU on linux host. Usually the VM is being updated to the latest snapshot once per 10 days. Everything was OK with with 2019-04-21 snapshot. The problem has been appeared since 2019-05-01 snapshot. The VM is installed on a dedicated drive with FDE. It is detected as sd0 by bsd.rd booted from install65.iso. But once installer is started the drive disappears. Here is full output: >> OpenBSD/amd64 CDBOOT 3.43 boot> cannot open cd0a:/etc/random.seed: No such file or directory booting cd0a:/6.5/amd64/bsd.rd: 3691345+1532928+3889096+0+598016 [373454+128+451752+300829]=0xa58318 entry point at 0x81001000 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.5-current (RAMDISK_CD) #50: Fri May 31 20:22:49 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 2130558976 (2031MB) avail mem = 2062069760 (1966MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5b10 (9 entries) bios0: vendor SeaBIOS version "1.12.0-20181126_142135-anatol" date 04/01/2014 bios0: QEMU Standard PC (i440FX + PIIX, 1996) acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: QEMU Virtual CPU version 2.5+, 2295.00 MHz, 06-06-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: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: apic clock running at 1000MHz ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpicpu at acpi0 not configured "ACPI0006" at acpi0 not configured "PNP0A03" at acpi0 not configured 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 pvbus0 at mainbus0: KVM pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 "Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured 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) pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 "Intel 82371AB Power" rev 0x03 at pci0 dev 1 function 3 not configured vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02 vga1: aperture needed wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio0: address 08:00:27:77:c1:d5 virtio0: msix shared virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio1 scsibus0 at vioblk0: 2 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed sd0: 114473MB, 512 bytes/sector, 234441632 sectors virtio1: msix shared virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 virtio2: no matching child driver; not configured ahci0 at pci0 dev 7 function 0 "Intel 82801I AHCI" rev 0x02: apic 0 int 11, AHCI 1.0 ahci0: port 0: 1.5Gb/s scsibus1 at ahci0: 32 targets cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable usb0 at uhci0: USB revision 1.0 uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 addr 1 isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay1 softraid0 at root scsibus2 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/amd64 6.5 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # bioctl -c C -l /dev/sd0a softraid0 bioctl: could not open /dev/sd0a: No such file or directory # ls /dev MAKEDEV cua01 klogrcd0c rrd0c rwd0g rwd0o ttyC0 wd0gwd0o bio diskmap kmemrd0arst0rwd0h rwd0p urandom wd0hwd0p bpf enrst0 ksyms rd0crwd0a rwd0i stderr wd0awd0iwskbd0 bpf0erst0 mem rfd0a rwd0b rwd0j stdin wd0bwd0jwskbd1 cd0afd0anrst0 rfd0b rwd0c rwd0k stdout wd0cwd0kwskbd2 cd0cfd0bnullrfd0c rwd0d rwd0l tty wd0dwd0lxf86 console fd0crandom rfd0i rwd0e rwd0m tty00 wd0ewd0mzero cua00 fd0ircd0a rrd0a rwd0f rwd0n tty01 wd0fwd0n Does anyone know the cause of this problem? Thanks. -- MS
Re: Prefered manpage idioms?
Hi, while these technicalities do exist in POSIX, it is better if understanding a manual page does not require paying attentions to them. In my opinion, the idiom that is simplest too understand is just the .Ar foo argument and the .Fl x option and then it is usually obvious from the context (from the item head in an option list or from the SYNOPSIS) whether "foo" is an option-argument or an operand. In the unusual case where confusion between option-arguments and operands is likely to arise and to cause users to construct a command incorrectly, using the term "option-argument" is probably sufficient to make it clear that the argument cannot be given without the option, because the term is somewhat self-explanatory. On the other hand, merely talking about an "operand" when the misconception could arise that the argument is an option-argument is probably not sufficient because the official term is somewhat non-obvious. Such (rare) cases likely need a more explicit wording, but that depends on the individual situation. That said, i agree with Jason that there is no need to change existing uses of "operand" (like in echo(1)) or to complain when people use the term in a manual page, even though i probably wouldn't use it. Yours, Ingo Andreas Kusalananda Kaehaeri wrote on Thu, May 30, 2019 at 02:32:00PM +0200: > On Thu, May 30, 2019 at 10:16:12PM +1000, Stephen Gregoratto wrote: >> When I'm writing new manpages, I like to draw inspiration from the >> documentation of similar programs. The problem is that many manpages >> have different ways of saying the same thing, probably due to their >> authors and time period they were written in. >> >> So, I'd like to ask what your preferred choice is of the following >> common idioms I keep finding: >[cut] >> 3. Program arguments >> >> Is it: >> Argument >> echo(1) >> Operand >> printf(1), also echo(1)? > An argument to a command can be one of three things: > > 1. An option > 2. An option-argument > 3. An operand > > An option is an argument that starts with a dash. An option-argument is > an argument to an option that takes an argument. An operand is an > argument that is not an option or an option-argument. > > Example: > > man -M path ls > > * -M is an option > * path is an option-argument to the -M option > * ls is an operand since it's neither an option nor an option-argument. > > POSIX: > > Argument: "In the shell command language, a parameter passed to a > utility as the equivalent of a single string in the argv array created > by one of the exec functions. An argument is one of the options, > option-arguments, or operands following the command name." > > Option: "An argument to a command that is generally used to specify > changes in the utility's default behavior." > > Option-argument: "A parameter that follows certain options. In some > cases an option-argument is included within the same argument string as > the option-in most cases it is the next argument." > > Operand: "An argument to a command that is generally used as an object > supplying information to a utility necessary to complete its processing. > Operands generally follow the options in a command line." > > > https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
Re: Let's Encrypt ACMEv1 end-of-life
> On May 31, 2019, at 10:42 AM, Diogo Pinela wrote: > > As I understand it, acme-client currently only supports > ACMEv1. Let's Encrypt recently announced they're going > to begin progressively deprecating that protocol starting > this November: OCSP is an interesting subject. In my opinion there is still a need for a certificate infrastructure inside private LAN's. I’ve learned that in many situations a DNS authority can not be accommodated & certs are non-op. In addition I find the reliance on public API via browser a potential privacy concern. Regards Patrick
amd64 snapshot very broken (Jun 1 02:24:13)
The amd64 snapshot with BUILDINFO Build date: 1559355853 - Sat Jun 1 02:24:13 UTC 2019 is very broken. Specifically, the boot loader is broken. If you upgrade and the new boot(8) is installed, you may no longer be able to boot the machine. Recovering from this will require booting from a different medium. i386 may also be affected. -- Christian "naddy" Weisgerber na...@mips.inka.de
