Updating src tree:
P src/bin/sh/parser.c
P src/common/lib/libc/arch/i386/string/strlen.S
P src/common/lib/libc/arch/x86_64/string/strlen.S
P src/distrib/notes/Makefile.inc
P src/distrib/notes/sparc/install
P src/games/trek/DOC/trekmanual.nr
P src/games/trek/USD.doc/trek.me
P src/include/arpa/name
At Wed, 8 Dec 2021 11:36:17 -0800, Jason Thorpe wrote:
Subject: Re: backward compatibility: how far can it reasonably go?
>
>
> > On Dec 8, 2021, at 10:52 AM, Greg A. Woods
> > wrote:
> > That's one bullet I've dodged entirely already since my oldest
> > systems are running netbsd-5 stable. (Th
Jason Thorpe writes:
>> On Dec 8, 2021, at 10:52 AM, Greg A. Woods wrote:
>>
>> That's one bullet I've dodged entirely already since my oldest systems
>> are running netbsd-5 stable. (Though in theory isn't there supposed to
>> be COMPAT support for SA?)
>
> int
> compat_60_sys_sa_register(lwp
> On Dec 8, 2021, at 10:52 AM, Greg A. Woods wrote:
>
> That's one bullet I've dodged entirely already since my oldest systems
> are running netbsd-5 stable. (Though in theory isn't there supposed to
> be COMPAT support for SA?)
int
compat_60_sys_sa_register(lwp_t *l,
const struct com
At Wed, 08 Dec 2021 11:08:09 -0500, Brad Spencer wrote:
Subject: Re: backward compatibility: how far can it reasonably go?
>
> When I took a system from 4.0 to 7.x some time ago, the only thing that
> I had problems with was anything that used scheduler activations since
> that had been removed.
At Wed, 8 Dec 2021 15:32:24 -, ya...@sdf.org wrote:
Subject: Re: backward compatibility: how far can it reasonably go?
>
> > "Greg A. Woods" writes:
no, Greg Troxel wrote:
> > I am unclear if ipf has been removed by default from current.
> Even in NetBSD 9, ipf is not in the GENERIC kernel
Brad Spencer writes:
> You can also shut the DOMU down and present the disks to another DOMU in
> real time using "xl block-attach " just use the "r" device if you
> use devices or the file otherwise. I have done this for many years with
> PV DOMUs on many different Xen versions. Once you
"Greg A. Woods" writes:
> At Tue, 7 Dec 2021 20:37:26 -0800 (PST), Paul Goyette
> wrote:
> Subject: Re: backward compatibility: how far can it reasonably go?
>>
>> Without looking at the details of your backtrace, the issue with
>> ifconfig(8) could be related to PRs kern/54150 and/or kern/5415
"Greg A. Woods" writes:
> So I've got a couple of old but important machines (Xen amd64 domUs)
> running NetBSD-5, and I've finally decided that I'm reasonably well
> enough prepared to try upgrading them.
>
> However it seems a "modern" (9.99.81, -current from about 2021-03-10)
> kernel with COM
> "Greg A. Woods" writes:
> I am unclear if ipf has been removed by default from current.
>
Even in NetBSD 9, ipf is not in the GENERIC kernel config.
Was the kernel compiled to use ipf?
e.g. add to kernel config:
options IPFILTER_LOG# ipmon(8) log support
options IPFILTER_L
"Greg A. Woods" writes:
> So I've got a couple of old but important machines (Xen amd64 domUs)
> running NetBSD-5, and I've finally decided that I'm reasonably well
> enough prepared to try upgrading them.
>
> However it seems a "modern" (9.99.81, -current from about 2021-03-10)
> kernel with CO
11 matches
Mail list logo
