On 25/12/19 10:30 pm, Sriram Narayanan wrote:
> On Wed, 25 Dec 2019 at 7:41 PM, Stuart Longland
> wrote:
>
>> Both VMs should probably be re-built from scratch as a matter of sanity,
>> but I can do that at leisure now, what I have, works.
>
>
> What hypervisor are you using? Does it support
On Wed, 25 Dec 2019 at 7:41 PM, Stuart Longland
wrote:
> On 24/12/19 9:16 pm, Dumitru Moldovan wrote:
> > Maybe it would be worth mentioning in the FAQ? I could only find it
> > here: https://www.openbsd.org/faq/upgrade63.html, but then it was not
> > mentioned for newer releases.
> >
> >
On 24/12/19 9:16 pm, Dumitru Moldovan wrote:
> Maybe it would be worth mentioning in the FAQ? I could only find it
> here: https://www.openbsd.org/faq/upgrade63.html, but then it was not
> mentioned for newer releases.
>
> Another remedy is to follow the `Files to remove` section in the FAQ,
>
On Mon, Dec 23, 2019 at 10:42:47PM +, rgci...@disroot.org wrote:
December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
Later that got updated to 6.2,
On 24/12/19 12:51 pm, Edgar Pettijohn wrote:
>
> On Dec 23, 2019 4:42 PM, rgci...@disroot.org wrote:
>>
>> December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
>> one thing that is useful is sysclean(8)
>>
>> my process now after a doas sysupgrade is
>> 1) doas sysclean; and review the output
>>
On Dec 23, 2019 4:42 PM, rgci...@disroot.org wrote:
>
> December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
>
> > On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
> >
> >> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
> >> Later that got updated to
On Mon, Dec 23, 2019 at 3:10 PM Stuart Longland
wrote:
...
> Where do you get `sysclean` from? I don't seem to have it:
> > sjl-router# man sysclean
>
> > man: No entry for sysclean in the manual.
> > sjl-router# which sysclean
> > which: sysclean: Command not found.
>
$ pkg_info sysclean
On 24/12/19 8:42 am, rgci...@disroot.org wrote:
>> My understanding is that this is by design. In an update, some libs are
>> overwritten (if they keep the same file name), but others are left on
>> disk (theoretically unused) when lib versions are incremented. I can
>> see a few ways in which
December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
> On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
>
>> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
>> Later that got updated to 6.2, then 6.3, 6.4…
>>
>> Yesterday I updated it to 6.5, then 6.6…
On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
Later that got updated to 6.2, then 6.3, 6.4…
Yesterday I updated it to 6.5, then 6.6… now I'm trying to run syspatch:
I have a similar issue with my
Stuart Longland writes:
> > 16 partitions:
> > #size offset fstype [fsize bsize cpg]
> > a: 268416 64 4.2BSD 2048 16384 2097 # /
> > b: 373010 268480swap# none
> > c: 16777216
Hi all,
So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
Later that got updated to 6.2, then 6.3, 6.4…
Yesterday I updated it to 6.5, then 6.6… now I'm trying to run syspatch:
> sjl-router# syspatch
>
12 matches
Mail list logo
