On 5/2/21 2:24 PM, Why 42? The lists account. wrote:
> The second item (right after the separator) on this page:
>
> https://www.openbsd.org/faq/upgrade69.html
>
> Reads: "[FAQ Index] | [6.7 -> 6.8]"
>
> Probably that should be 6.8 -> 6.9 ?
>
> Otherwise looking good, just sysupgraded from
I mean use the usb stick for the files mormozoid. boot using bsd.rd and
at the "upgrade" prompt instead of selecting http mount your drive and
select "disk" and type in the location of the mount
On Sun May 2, 2021 at 12:34 PM CST, Luke Small wrote:
> There has to be a valid partition to install it
Am Sun, May 02, 2021 at 11:49:10PM +0200 schrieb Why 42? The lists account.:
>
> Actually I do notice one thing, having just upgraded to:
> kern.version=OpenBSD 6.9-current (GENERIC.MP) #492: Sat May 1 17:37:28 MDT
> 2021
>
> I checked the output from dmesg and I have a new boot time message:
No you don't chudazoid, you just select your usb disk with the file sets
after selecting "disk" as your file location
On Sat May 1, 2021 at 7:37 PM CST, Luke Small wrote:
> I would do that, but I’ll have to figure out how to manually mount my
> encrypted partition, which sysupgrade and bsd.rd
Actually I do notice one thing, having just upgraded to:
kern.version=OpenBSD 6.9-current (GENERIC.MP) #492: Sat May 1 17:37:28 MDT 2021
I checked the output from dmesg and I have a new boot time message:
dt: 443 probes
man dt tells me that dt is dynamic tracing and that I can enable it by
The second item (right after the separator) on this page:
https://www.openbsd.org/faq/upgrade69.html
Reads: "[FAQ Index] | [6.7 -> 6.8]"
Probably that should be 6.8 -> 6.9 ?
Otherwise looking good, just sysupgraded from a snapshot, everything
seems to be working perfectly so far.
Thanks
I didn’t think of that one. I’ll try to remember that in the future.
On Sun, May 2, 2021 at 4:19 PM jpeg bild wrote:
> I mean use the usb stick for the files mormozoid. boot using bsd.rd and
> at the "upgrade" prompt instead of selecting http mount your drive and
> select "disk" and type in the
FWIW, I run a server with -current. That always has some small risks
(which I haven't run into at all for a long time! +1 developers!!!)
Because of those possibilities, I added a second bootable backup disk.
I intend to keep running -current. I will now put 6.9-stable on the
second disk. This
That change to undo the “supersede” command to look at the local unbound
server in dhclient.conf fixed it.
Downloading 6.9 release as we speak.
On Sun, May 2, 2021 at 1:34 PM Luke Small wrote:
> There has to be a valid partition to install it to. When I have an
> encrypted drive, that doesn’t
There has to be a valid partition to install it to. When I have an
encrypted drive, that doesn’t exist using usb…chudazoid.
On Sun, May 2, 2021 at 1:31 PM jpeg bild wrote:
> No you don't chudazoid, you just select your usb disk with the file sets
> after selecting "disk" as your file location
>
On 2021-05-02, jpeg bild wrote:
> worked fine for me, its basically just reinstalling but with the same
> configuration as your last install
"not supported" does not mean "_won't_ work", it means "if you try this
and break things, we aren't going to try and change anything to accommodate
you,
On 2021-05-02, Luke Small wrote:
> I have a simple network setup of google fiber with a modem/router at
> 196.168.1.1 which the default pf.conf should work instead of my pretty
> complicated (for a home network) pf.conf . I have no clue why the bsd.rd
> doesn’t work anymore…unless the
> On 2 May 2021, at 14:56, Dave Voutila wrote:
>
>
> Mischa Peters writes:
>
On 2 May 2021, at 14:25, Dave Voutila wrote:
>>>
>>>
>>> Mischa writes:
>>>
Interestingly I am seeing the same on my 6.9 hosts, except the host
running -current.
>>>
>>> Hmm. -current
Mischa Peters writes:
>> On 2 May 2021, at 14:25, Dave Voutila wrote:
>>
>>
>> Mischa writes:
>>
>>>
>>> Interestingly I am seeing the same on my 6.9 hosts, except the host running
>>> -current.
>>
>> Hmm. -current has some small changes to virtio emulation, specifically
>> fixing some bad
> On 2 May 2021, at 14:25, Dave Voutila wrote:
>
>
> Mischa writes:
>
>>
>> Interestingly I am seeing the same on my 6.9 hosts, except the host running
>> -current.
>
> Hmm. -current has some small changes to virtio emulation, specifically
> fixing some bad casts I found [1]. That might
Mischa writes:
>
> Interestingly I am seeing the same on my 6.9 hosts, except the host running
> -current.
Hmm. -current has some small changes to virtio emulation, specifically
fixing some bad casts I found [1]. That might explain the difference
with -current.
> The hosts are similar in
hi
on host
/etc 3>cat hostname.bridge1
rdomain 10
group vpn
add vether1
#add em1
up
/etc 4>cat vm.conf
switch "vswitch1" {
interface bridge1
rdomain 10
enable
}
vm "vpngw" {
owner _vmd
disk "/home/vmd/disk0.qcow2"
interface {
On Sun, May 02, 2021 at 08:55:27AM +0200, Federico Giannici wrote:
> SHORT VERSION: How can I make Chromium to use the speakers from the internal
> soundcard and the the microphone from an USB card?
You could do what you want with AUDIORECDEVICE environment variable
(see sndio(4) man page).
$
On 2 May at 13:04, Dave Voutila wrote:
> Holger Glaess writes:
>
> > hi
> >
> >
> > i did the upgrade von 6.8 to 6.9 .
> >
> >
> > after reboot i get in my messages log
> >
> >
> > vmd[56]: vionet_enq_rx: descriptor too small for packet data
> >
> >
> > i run only one vm on my box, this is also
Holger Glaess writes:
> hi
>
>
> i did the upgrade von 6.8 to 6.9 .
>
>
> after reboot i get in my messages log
>
>
> vmd[56]: vionet_enq_rx: descriptor too small for packet data
>
>
> i run only one vm on my box, this is also upgraded to 6.9.
>
>
> how can i fix this ?
>
>
Can you share some
On Sun, May 02, 2021 at 08:55:27AM +0200, Federico Giannici wrote:
> SHORT VERSION: How can I make Chromium to use the speakers from the internal
> soundcard and the the microphone from an USB card?
According to this thread on @misc from 2020, you cannot. Not yet at
least. See the answers from
hi
i did the upgrade von 6.8 to 6.9 .
after reboot i get in my messages log
vmd[56]: vionet_enq_rx: descriptor too small for packet data
i run only one vm on my box, this is also upgraded to 6.9.
how can i fix this ?
Holger
SHORT VERSION: How can I make Chromium to use the speakers from the
internal soundcard and the the microphone from an USB card?
LONG VERSION:
I'd like to use my OpenBSD 6.9 amd64 PC for videoconferencing using
Google Meets in Chromium. The problem is that I have the speakers
connected to the
23 matches
Mail list logo
