"Emmanuel Dreyfus" writes:
> Log Message:
> Primary bootstrap is now able to read a GPT inside RAIDframe.
did you also update documentation?
Nia Alarie wrote in
<20230629214647.db217f...@cvs.netbsd.org>:
|Module Name: src
|Committed By: nia
|Date: Thu Jun 29 21:46:47 UTC 2023
|
|Modified Files:
| src/doc: CHANGES
|
|Log Message:
|ch-ch-changes
station to station
--steffen
|
|Der Kragenbaer,The moon
> Date: Thu, 29 Jun 2023 16:51:05 - (UTC)
> From: chris...@astron.com (Christos Zoulas)
>
> In article <20230628222148.710dbf...@cvs.netbsd.org>,
> Thomas Klausner wrote:
> >-=-=-=-=-=-
> >
> [...]
>
In article <20230628222148.710dbf...@cvs.netbsd.org>,
Thomas Klausner wrote:
>-=-=-=-=-=-
>
[...]
>+-DTMUX_CONF='"/etc/tmux.conf:~/.tmux.conf:$XDG_CONFIG_HOME/tmux/tmux.conf:~/.config/tmux/tmux.conf"'
> \
What is XDG_CONFIG_HOME?
christos
On 23-06-11 15:38, Valery Ushakov wrote:
| On Sun, Jun 11, 2023 at 22:19:42 +1000, Luke Mewburn wrote:
| > My goal is to get the mk.conf(5) up to date and correct, and more usable.
| > I intend to remove the duplication in BUILDING and bsd.README
| > and refer back to mk.conf(5) to avoid
On Sun, Jun 11, 2023 at 11:23:23AM +0300, Kimmo Suominen wrote:
> My thinking here is that it makes it simpler to keep the script in
> sync between branches. (I have not checked, but I guess the sysctl
> does not depend on kernel configuration then.)
In this special case I think this would not be
On Sun, Jun 11, 2023 at 22:19:42 +1000, Luke Mewburn wrote:
> | I'm not sure what do you mean. The difference between .Ss and .Sh is
> | only the indent:
>
> Ahh, you're right, I misspoke. Tired brain when working on the commit.
>
> IMHO, they both suffer from lack of blank line there,
On 23-06-11 14:14, Valery Ushakov wrote:
| On Sun, Jun 11, 2023 at 10:44:33 +, Luke Mewburn wrote:
|
| > Module Name: src
| > Committed By: lukem
| > Date: Sun Jun 11 10:44:33 UTC 2023
| >
| > Modified Files:
| > src/share/man/man5: mk.conf.5
| >
|
On Sun, Jun 11, 2023 at 10:44:33 +, Luke Mewburn wrote:
> Module Name: src
> Committed By: lukem
> Date: Sun Jun 11 10:44:33 UTC 2023
>
> Modified Files:
> src/share/man/man5: mk.conf.5
>
> Log Message:
[...]
> Change sub headings to headings; it's easier to read.
> (I don't
On Sat, 10 Jun 2023 at 20:08, Martin Husemann wrote:
> I don't like this commit, it mixes:
>
> - several text improvements (good!)
> - one unrelated cosmetic change (rely on all rc.d scripts being installed
>with x bit, so drop the "sh" from the manual invocation)
Calling the rc.d script
On Sat, Jun 10, 2023 at 04:02:39AM +, Kimmo Suominen wrote:
> Module Name: src
> Committed By: kim
> Date: Sat Jun 10 04:02:39 UTC 2023
>
> Modified Files:
> src/etc/rc.d: sshd
>
> Log Message:
> Add some backwards compat. Adjust grammar.
>
>
> To generate a diff of this
Valery Ushakov wrote:
> I think that information *must* be there, as that's *the* place where
> the names are (un)parsed. I'm not sure whether this information has
> to be duplicated as-is in chflags(1), or whether chflags(1) can have a
> less verbose version.
Perhaps a simple
See
On Thu, May 25, 2023 at 09:59:41 -0400, Greg Troxel wrote:
> Taylor R Campbell writes:
>
> > jschauma@'s change did help clarify (1) and (2). Let's try to work
> > together to make it better?
[...]
> I would recommend:
>
> Noting that archive flag represents something in some foreign
>
Date:Thu, 25 May 2023 09:59:41 -0400
From:Greg Troxel
Message-ID:
| Also, the man page does not explain that because "nodump" is the name of
| a flag, one does "chflags dump foo" to remove the nodump flag.
It doesn't really need to, as while that works, so
Taylor R Campbell writes:
> jschauma@'s change did help clarify (1) and (2). Let's try to work
> together to make it better?
Well said.
I can shed a little light on some of the questions.
> 1. What is `arch' or `archived' supposed to mean? Who sets it, who
>pays attention to it, and
> Date: Thu, 25 May 2023 15:10:41 +0300
> From: Valery Ushakov
>
> This new paragraph is wedged right between the list of the options and
> the continuation of that same paragraph that says that they can be
> prefixed with "no".
>
> A description of an obsolete flag right in the middle of the
Valery Ushakov wrote:
> Anyway, this change is strictly for the worse.
¯\_(ツ)_/¯
I've reverted the change.
-Jan
Valery Ushakov writes:
> On Thu, May 25, 2023 at 07:17:52 -0400, Greg Troxel wrote:
>
>> Jan Schaumann writes:
>>
>> > Valery Ushakov wrote:
>> >> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>> >
>> >> > Briefly describe the 'arch' and 'nodump' flags.
>> >>
>> >> What makes
On Thu, May 25, 2023 at 07:17:52 -0400, Greg Troxel wrote:
> Jan Schaumann writes:
>
> > Valery Ushakov wrote:
> >> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> >
> >> > Briefly describe the 'arch' and 'nodump' flags.
> >>
> >> What makes them special and why is that these
On Wed, May 24, 2023 at 23:44:07 -0400, Jan Schaumann wrote:
> Valery Ushakov wrote:
> > On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>
> > > Briefly describe the 'arch' and 'nodump' flags.
> >
> > What makes them special and why is that these two have to be described
> > here
Jan Schaumann writes:
> Valery Ushakov wrote:
>> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>
>> > Briefly describe the 'arch' and 'nodump' flags.
>>
>> What makes them special and why is that these two have to be described
>> here and not in chflags(2), where the flags are
Valery Ushakov wrote:
> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> > Briefly describe the 'arch' and 'nodump' flags.
>
> What makes them special and why is that these two have to be described
> here and not in chflags(2), where the flags are actually defined?
Unlike the
On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> Module Name: src
> Committed By: jschauma
> Date: Wed May 24 22:33:17 UTC 2023
>
> Modified Files:
> src/usr.bin/chflags: chflags.1
>
> Log Message:
> Briefly describe the 'arch' and 'nodump' flags.
What makes them
I experimented with this, and my analysis of the gnulib emacs regexp
wasn't quite correct.
When I reverted this autoconf change, and fixed m4 as below,
regen works. I'm testing a full build of NetBSD now.
On 23-05-25 06:36, Luke Mewburn wrote:
| Hi Christos,
|
| Whilst this initially
Hi Christos,
Whilst this initially fixed my tools/compat regen problem,
I'm not sure it's correct long term.
I think we need to revert this, and fix usr.bin/m4 -g (GNU)
emulation for m4 regexp() and patsubst() ?
A quick comparison of usr.bin/m4/gnum4.c twiddle() versus
On 23-05-17 01:35, Valery Ushakov wrote:
| Module Name:src
| Committed By: uwe
| Date: Wed May 17 01:35:00 UTC 2023
|
| Modified Files:
| src/usr.sbin/installboot: installboot.8
|
| Log Message:
| installboot(8): fix up markup
|
| Don't
On Sat, 20 May 2023 03:13:19 +1000, Luke Mewburn wrote:
> | Arguably fixes PR toolchain/42166
>
> I think you meant toolchain/41266.
Argh! Of course! Mis-typed once, and my fingers stuck with it.
Cheerio,
Hauke
--
Hauke Fath
Linnéweg 7
64342 Seeheim-Jugenheim
Germany
On 23-05-19 14:47, Hauke Fath wrote:
| Module Name:src
| Committed By: hauke
| Date: Fri May 19 14:47:16 UTC 2023
|
| Modified Files:
| src/distrib/cdrom: Makefile
| src/etc/etc.mac68k: Makefile.inc
|
| Log Message:
| Creating Type mappings
On Sat, May 06, 2023 at 08:43:20AM +, Nick Hudson wrote:
> Module Name: src
> Committed By: skrll
> Date: Sat May 6 08:43:20 UTC 2023
>
> Modified Files:
> src/distrib/sets/lists/dtb: ad.earmv7hfeb
>
> Log Message:
> Add imx6sx dtb files for BE too
Hum, I'm not sure that
> Date: Sun, 30 Apr 2023 07:27:34 +0700
> From: Robert Elz
>
> Date:Sat, 29 Apr 2023 23:30:18 +
> From:"Robert Elz"
> Message-ID: <20230429233018.cadf4f...@cvs.netbsd.org>
>
> | Modified Files:
> | src/sys/kern: vfs_subr.c
> | src/sys/sys: sdt.h
> |
Date:Sat, 29 Apr 2023 23:30:18 +
From:"Robert Elz"
Message-ID: <20230429233018.cadf4f...@cvs.netbsd.org>
| Modified Files:
| src/sys/kern: vfs_subr.c
| src/sys/sys: sdt.h
|
| Log Message:
| Fix builds (hopefully) when DTRACE hooks are not
Nikita wrote:
> Module Name: src
> Committed By: nikita
> Date: Mon Apr 17 21:17:58 UTC 2023
>
> Modified Files:
> src/external/mit/lua/dist/src: ldump.c lundump.c
>
> Log Message:
> lua: apply upstream bugfix for "Loading a corrupted binary file can segfault."
Unless it's a
Thanks!
rin
On 2023/04/18 22:53, Nikita Ronja Gillmann wrote:
Hi,
okay. I'll add them for now as notes in one of the README files in the lua
directory.
Rin Okuyama transcribed 0.4K bytes:
Hello again,
On 2023/04/18 4:16, Nikita wrote:
Module Name: src
Committed By: nikita
Date:
Hi,
On 2023/04/18 23:00, Nikita Ronja Gillmann wrote:
Rin Okuyama transcribed 1.9K bytes:
Also, why did you remove copyright notice in luahello.lua? IIUC, this
should be agreed by the copyright holder, even if the code in problem
seems trivial.
Please run a diff on revision 1.2 and 1.3 of
jk> mount_procfs(8): Document the format of the region descriptor
jk> lines contained in the 'map' and 'maps' special files.
This is to the best of my understanding, based on reading
the code and the UVM usenix paper [1].
Corrections welcome.
[1]: https://chuck.cranor.org/p/uvm_usenix.pdf
Rin Okuyama transcribed 1.9K bytes:
Hi,
On 2023/04/17 5:46, Nikita wrote:
Module Name:src
Committed By: nikita
Date: Sun Apr 16 20:46:18 UTC 2023
Modified Files:
src/distrib/sets/lists/base: ad.aarch64 mi shl.mi
src/distrib/sets/lists/debug: shl.mi
Rin Okuyama transcribed 1.9K bytes:
Hi,
On 2023/04/17 5:46, Nikita wrote:
Module Name:src
Committed By: nikita
Date: Sun Apr 16 20:46:18 UTC 2023
Modified Files:
src/distrib/sets/lists/base: ad.aarch64 mi shl.mi
src/distrib/sets/lists/debug: shl.mi
Hi,
okay. I'll add them for now as notes in one of the README files in the
lua directory.
Rin Okuyama transcribed 0.4K bytes:
Hello again,
On 2023/04/18 4:16, Nikita wrote:
Module Name:src
Committed By: nikita
Date: Mon Apr 17 19:16:38 UTC 2023
Modified Files:
Hello again,
On 2023/04/18 4:16, Nikita wrote:
Module Name:src
Committed By: nikita
Date: Mon Apr 17 19:16:38 UTC 2023
Modified Files:
src/external/mit/lua/dist/src: lua.c
Log Message:
lua: Apply upstream bugfix for "lua.c assumes that argv has at least one
element."
Hi,
On 2023/04/17 5:46, Nikita wrote:
Module Name:src
Committed By: nikita
Date: Sun Apr 16 20:46:18 UTC 2023
Modified Files:
src/distrib/sets/lists/base: ad.aarch64 mi shl.mi
src/distrib/sets/lists/debug: shl.mi
src/doc: 3RDPARTY CHANGES
> Date: Tue, 11 Apr 2023 21:50:49 +0200
> From: Michael van Elst
>
> On Wed, Apr 12, 2023 at 01:10:40AM +0700, Robert Elz wrote:
> >
> > | In that state then decrementing dk_rawopens beyond zero will make
> > | dklastclose do the right thing: nothing.
> >
> > Except that if that happens,
> Module Name:src
> Committed By: mlelstv
> Date: Mon Apr 10 15:26:57 UTC 2023
>
> Modified Files:
> src/sys/dev/usb: uvideo.c uvideoreg.h
>
> Log Message:
> Better descriptor parsing.
How is it better? What problems does it fix?
> Add sanity check if no default format
On Wed, Apr 12, 2023 at 01:10:40AM +0700, Robert Elz wrote:
>
> | In that state then decrementing dk_rawopens beyond zero will make
> | dklastclose do the right thing: nothing.
>
> Except that if that happens, dk_rawopens will be left == ~0 and the next
> open attempt will then increment it,
Date:Tue, 11 Apr 2023 17:21:17 +0200
From:Michael van Elst
Message-ID:
| In that state then decrementing dk_rawopens beyond zero will make
| dklastclose do the right thing: nothing.
Except that if that happens, dk_rawopens will be left == ~0 and the next
open
On Tue, Apr 11, 2023 at 09:07:49AM +, Taylor R Campbell wrote:
>
> (a) how we can legitimately enter a state where the assertions are
> violated, and
dklastclose is called when the close operation ends in no more openers.
There is nothing that guarantees that any open was successful
> Module Name:src
> Committed By: mlelstv
> Date: Tue Sep 27 17:04:52 UTC 2022
>
> Modified Files:
> src/sys/dev/dkwedge: dk.c
>
> Log Message:
> Remove bogus assertions.
>
> @@ -1221,8 +1221,6 @@ dklastclose(struct dkwedge_softc *sc)
>
>
On Thu, Mar 30, 2023 at 10:39:31 +, Taylor R Campbell wrote:
> Modified Files:
> src/share/misc: style
>
> Log Message:
> style(5): Forbid extern in .c files.
>
> Discussed on tech-userlevel (bcc tech-kern):
> https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
I
On Tue, Mar 28, 2023 at 22:13:25 +0200, Roland Illig wrote:
> Am 28.03.2023 um 19:52 schrieb Valery Ushakov:
> > On Tue, Mar 28, 2023 at 14:44:36 +, Roland Illig wrote:
> >
> > > lint: warn about extern declarations outside headers
> >
> > vs.
> >
> > >
Am 28.03.2023 um 19:52 schrieb Valery Ushakov:
On Tue, Mar 28, 2023 at 14:44:36 +, Roland Illig wrote:
lint: warn about extern declarations outside headers
vs.
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
which is nested extern declaration inside a function
On Tue, Mar 28, 2023 at 14:44:36 +, Roland Illig wrote:
> lint: warn about extern declarations outside headers
vs.
> https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
which is nested extern declaration inside a function body.
I.e. the two lines of this log message
"Taylor R Campbell" writes:
> Module Name: src
> Committed By: riastradh
> Date: Mon Mar 13 18:18:36 UTC 2023
>
> Modified Files:
> src/lib/libm/src: ldbl_dummy.c
>
> Log Message:
> libm: Fill in more dummy long double transcendental functions.
>
> This should cover everything from
> On Mar 1, 2023, at 2:25 PM, Steffen Nurpmeso wrote:
>
> Jason R Thorpe wrote in
> <20230301040454.c3b17f...@cvs.netbsd.org>:
> |Module Name: src
> |Committed By: thorpej
> |Date: Wed Mar 1 04:04:54 UTC 2023
> |
> |Modified Files:
> | src/share/misc: acronyms.comp
> |
> |Log
Jason R Thorpe wrote in
<20230301040454.c3b17f...@cvs.netbsd.org>:
|Module Name: src
|Committed By: thorpej
|Date: Wed Mar 1 04:04:54 UTC 2023
|
|Modified Files:
| src/share/misc: acronyms.comp
|
|Log Message:
|Add NHACP (NABU HCCA Application Communication Protocol)
NABU is
Taylor R Campbell wrote:
> That said, I don't see any reason why this should be a macro in the
> first place. If there is a compelling reason, please write it down;
> if not, please change it to a static function:
>
Sure.
> static BuildMon *
> BM(Job *job)
> {
>
> return (job != NULL
> Module Name:src
> Committed By: sjg
> Date: Sat Feb 25 22:52:22 UTC 2023
>
> Modified Files:
> src/usr.bin/make: meta.c
>
> Log Message:
> meta.c: use macro to access job->bm
>
> and if job is NULL use Mybm.
> +#define BM(job) (job != NULL) ? >bm :
If this must be a
On Mon, Feb 20, 2023 at 15:41:04 +0100, Martin Husemann wrote:
> On Mon, Feb 20, 2023 at 05:15:33PM +0300, Valery Ushakov wrote:
> > them up, b/c you cannot amend that comment. To add to the fun, I
> > think releng scripts just clone the commit message on pull ups, so
> > that comment gets
On Mon, Feb 20, 2023 at 22:35:40 +0700, Robert Elz wrote:
> Date:Mon, 20 Feb 2023 16:47:01 +0300
> From:Valery Ushakov
> Message-ID:
>
> | I wonder if we should stop abusing commit messages as pull-up
> | reminders. These XXX will not convey any useful
Date:Mon, 20 Feb 2023 16:47:01 +0300
From:Valery Ushakov
Message-ID:
| I wonder if we should stop abusing commit messages as pull-up
| reminders. These XXX will not convey any useful information a few
| months down the line...
I think they're useful (if only
On Mon, Feb 20, 2023 at 05:15:33PM +0300, Valery Ushakov wrote:
> them up, b/c you cannot amend that comment. To add to the fun, I
> think releng scripts just clone the commit message on pull ups, so
> that comment gets splattered all over the target branches too.
Yes - I try to manually remove
On Mon, Feb 20, 2023 at 13:57:32 +, Taylor R Campbell wrote:
> > > XXX pullup-8
> > > XXX pullup-9
> > > XXX pullup-10
> >
> > I wonder if we should stop abusing commit messages as pull-up
> > reminders. These XXX will not convey any useful information a few
> > months down the line...
>
>
> Date: Mon, 20 Feb 2023 16:47:01 +0300
> From: Valery Ushakov
>
> On Mon, Feb 20, 2023 at 13:30:23 +, Taylor R Campbell wrote:
>
> > Module Name:src
> > Committed By: riastradh
> > Date: Mon Feb 20 13:30:23 UTC 2023
> >
> > Modified Files:
> >
On Mon, Feb 20, 2023 at 13:30:23 +, Taylor R Campbell wrote:
> Module Name: src
> Committed By: riastradh
> Date: Mon Feb 20 13:30:23 UTC 2023
>
> Modified Files:
> src/sys/arch/sparc64/sparc64: lock_stubs.s
>
> Log Message:
> sparc64: Add missing LoadStore ordering for
On Tue, 14 Feb 2023 at 14:45, Martin Husemann wrote:
> On Tue, Feb 14, 2023 at 11:39:23PM +0900, Izumi Tsutsui wrote:
> > > Module Name:src
> > > Committed By: abs
> > > Date: Sun Feb 12 19:18:41 UTC 2023
> > >
> > > Modified Files:
> > >
On Tue, Feb 14, 2023 at 11:39:23PM +0900, Izumi Tsutsui wrote:
> > Module Name:src
> > Committed By: abs
> > Date: Sun Feb 12 19:18:41 UTC 2023
> >
> > Modified Files:
> > src/distrib/i386/installimage: install.sh
> >
> > Log Message:
> > Switch install.sh to use
> Module Name: src
> Committed By: abs
> Date: Sun Feb 12 19:18:41 UTC 2023
>
> Modified Files:
> src/distrib/i386/installimage: install.sh
>
> Log Message:
> Switch install.sh to use /usr/sbin/sysinst for sysinst rather than ./sysinst
>
> Matches i386/cdroms/install.sh and
On Wed, Feb 08, 2023 at 12:09:54 -0500, David H. Gutteridge wrote:
> > In postscript output Pq has different spacing than literal () (in
> > other entries around it).
>
> I wondered if there could be a difference. Which format do you prefer?
> (My inclination would just be to use literal
On Wed, 2023-02-08 at 01:18 +0300, Valery Ushakov wrote:
> On Tue, Feb 07, 2023 at 01:17:41 +, David H. Gutteridge wrote:
>
> > Module Name:src
> > Committed By: gutteridge
> > Date: Tue Feb 7 01:17:41 UTC 2023
> >
> > Modified Files:
> > src/share/man/man4: bpf.4
>
On Tue, Feb 07, 2023 at 01:17:41 +, David H. Gutteridge wrote:
> Module Name: src
> Committed By: gutteridge
> Date: Tue Feb 7 01:17:41 UTC 2023
>
> Modified Files:
> src/share/man/man4: bpf.4
>
> Log Message:
> bpf.4: fix a garbled item heading
>
> Make the BIOCSDIRECTION
"Christos Zoulas" writes:
> Module Name: src
> Committed By: christos
> Date: Tue Feb 7 20:39:03 UTC 2023
>
> Modified Files:
> src/external/gpl3/binutils/dist/bfd: config.bfd elfn32-mips.c
note that the config.bfd changes here now mean there are two
copies of all 4 mips*netbsd*
Date:Tue, 24 Jan 2023 14:51:03 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Once we add them older kernels will break,
I doubt that they'd break any kernels - curses using programs using
these sequences with an old kernel might break
On Tue, 24 Jan 2023 at 14:51, Christos Zoulas wrote:
>
> In article ,
> Valery Ushakov wrote:
> >On Wed, Jan 18, 2023 at 12:02:17 -0500, Christos Zoulas wrote:
> >
> >> Module Name: src
> >> Committed By:christos
> >> Date:Wed Jan 18 17:02:17 UTC 2023
> >>
> >> Modified
In article ,
Valery Ushakov wrote:
>On Wed, Jan 18, 2023 at 12:02:17 -0500, Christos Zoulas wrote:
>
>> Module Name: src
>> Committed By:christos
>> Date:Wed Jan 18 17:02:17 UTC 2023
>>
>> Modified Files:
>> src/sys/dev/wscons: wsemul_vt100_subr.c
>>
>> Log
On Wed, Jan 18, 2023 at 12:02:17 -0500, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Wed Jan 18 17:02:17 UTC 2023
>
> Modified Files:
> src/sys/dev/wscons: wsemul_vt100_subr.c
>
> Log Message:
> Add rin, indn, vpa, hpa, and cbt terminfo capabilities
On Wed, Jan 18, 2023 at 11:54:57AM +, David Brownlee wrote:
> Adding an explicit -E seemed like the simplest and smallest
I missed the part that kre explained: this is not a login shell,
so indeed your change is the most simple solution.
Martin
On Tue, 17 Jan 2023 at 08:57, Robert Elz wrote:
>
> Date:Tue, 17 Jan 2023 08:13:12 +0100
> From:Martin Husemann
> Message-ID: <20230117071312.ga18...@mail.duskware.de>
>
> | what is missing in this
> | environment so it does not work by default?
>
> The shell
Date:Tue, 17 Jan 2023 08:13:12 +0100
From:Martin Husemann
Message-ID: <20230117071312.ga18...@mail.duskware.de>
| what is missing in this
| environment so it does not work by default?
The shell started this way is not a login shell, so does
not read any of the
On Mon, Jan 16, 2023 at 03:00:03PM +, David Brownlee wrote:
> Module Name: src
> Committed By: abs
> Date: Mon Jan 16 15:00:03 UTC 2023
>
> Modified Files:
> src/distrib/amd64/cdroms: install.sh
> src/distrib/amd64/installimage: install.sh
>
On Sun, 15 Jan 2023 19:14:14 +0100, Roland Illig writes:
>It is really unfortunate that make didn't catch this typo by itself.
>
>.if ${MACHINE_ARCH} =3D=3D "x86_64" || \
> ${MACHINE_ARCH} =3D=3D "i386" || \
> ${MACHINE_ARCH} =3D=3D "alpha" || \\
> !empty(MACHINE_ARCH:Maarch64*) || \
>
Am 15.01.2023 um 11:51 schrieb Nick Hudson:
Module Name:src
Committed By: skrll
Date: Sun Jan 15 10:51:04 UTC 2023
Modified Files:
src/share/mk: bsd.own.mk
Log Message:
Really switch aarch64 and sparc binutils to 2.39
To generate a diff of this commit:
cvs rdiff -u
That's very funny. Yes I think we should warn. I don't think that \\ should
be a valid variable name.
Best,
christos
> On Jan 15, 2023, at 1:14 PM, Roland Illig wrote:
>
> Am 15.01.2023 um 11:51 schrieb Nick Hudson:
>> Module Name: src
>> Committed By:skrll
>> Date:Sun
"Jonathan A. Kollasch" writes:
> Module Name: src
> Committed By: jakllsch
> Date: Thu Jan 5 02:38:51 UTC 2023
>
> Modified Files:
> src/sys/net: if_wg.c
>
> Log Message:
> Check for authorization for SIOCSDRVSPEC and SIOCGDRVSPEC ioctls for wg(4).
>
> Addresses PR 57161.
might be
> Modified Files:
> src/sys/conf: copyright
>
> Log Message:
> Welcome to 2023. Wrap lines so the years fit in to 80 columns with
> a leading kernel log timestamp.
Please don't forget requesting pullup to all release branches.
Thanks,
---
Izumi Tsutsui
Requested!
christos
> On Dec 24, 2022, at 6:09 AM, Alexander Nasonov wrote:
>
> Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Fri Dec 23 19:37:06 UTC 2022
>>
>> Modified Files:
>> src/usr.sbin/tprof: tprof_top.c
>>
>> Log Message:
>>
Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Fri Dec 23 19:37:06 UTC 2022
>
> Modified Files:
> src/usr.sbin/tprof: tprof_top.c
>
> Log Message:
> use malloc instead of alloca so that SSP works.
pullup to 10?
On Fri, 23 Dec 2022 01:59:17 Izumi Tsutsui wrote:
> > Module Name:src
> > Committed By: nat
> > Date: Thu Dec 22 11:05:55 UTC 2022
> >
> > Modified Files:
> > src/distrib/sets/lists/man: mi
> > src/share/man/man4: Makefile
> > src/sys/arch/alpha/conf:
> Module Name: src
> Committed By: nat
> Date: Thu Dec 22 11:05:55 UTC 2022
>
> Modified Files:
> src/distrib/sets/lists/man: mi
> src/share/man/man4: Makefile
> src/sys/arch/alpha/conf: GENERIC
> src/sys/arch/amd64/conf: ALL
> src/sys/arch/atari/conf:
On Tue, Dec 13, 2022 at 12:32:26AM +1100, matthew green wrote:
> "Michael van Elst" writes:
> > Module Name:src
> > Committed By: mlelstv
> > Date: Sun Dec 11 11:31:55 UTC 2022
> >
> > Modified Files:
> > src/sys/fs/autofs: autofs_vnops.c
> >
> > Log Message:
> >
"Michael van Elst" writes:
> Module Name: src
> Committed By: mlelstv
> Date: Sun Dec 11 11:31:55 UTC 2022
>
> Modified Files:
> src/sys/fs/autofs: autofs_vnops.c
>
> Log Message:
> Use genfs_pathconf for VOP_PATHCONF.
> Fixes bin/57103.
i see pathconf failures with puffs
Hi,
r1.125 of refresh.c breaks /usr/bin/vi for me.
When scrolling down long file with 'j' key and reaches the bottom
line, screen is not scrolled up and new lines are displayed
over the previous bottom line.
Could you take a look at my problem?
Thank you very much.
"Brett Lymn" writes:
>
In article <20221128024658.71caaf...@cvs.netbsd.org>,
Jan Schaumann wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: jschauma
>Date: Mon Nov 28 02:46:58 UTC 2022
>
>Modified Files:
> src/etc: protocols
>
>Log Message:
>regen from IANA 2022-09-28
>
>
>To generate a diff of
Taylor R Campbell writes:
[snip]
> The issue here isn't the duration of the delay -- just the mechanism.
> Sleeping for 35ms with kpause(9) is fine, but busy-waiting on the CPU
> for 35ms with delay(9) is not (unless HZ is set to something absurdly
> low like 10 instead of the usual 100, but I
> Date: Wed, 23 Nov 2022 01:42:13 -0500
> From: Brad Spencer
>
> Simon Burge writes:
>
> > + delay(35000);
> >
> > This will spin for 35 milliseconds (per sensor read if I read this
> > correctly). Can you please look at using kpause(9) for this delay?
> > See some other i2c drivers for
Simon Burge writes:
> Hi Brad,
>
>> Module Name: src
>> Committed By:brad
>> Date:Tue Nov 22 19:40:31 UTC 2022
>>
>> Modified Files:
>>
>> src/sys/dev/i2c: bmx280.c
>>
>> Log Message:
>>
>> Read the datasheet more closely and put in some delays. The chip will
>>
Hi Brad,
> Module Name: src
> Committed By: brad
> Date: Tue Nov 22 19:40:31 UTC 2022
>
> Modified Files:
>
> src/sys/dev/i2c: bmx280.c
>
> Log Message:
>
> Read the datasheet more closely and put in some delays. The chip will
> just return junk if the wait is not long enough to
On 15/11/2022 05:35, Ryo Shimizu wrote:
Since l2_sha continues to point outside of m_data manipulated by m_adj(),
it can be corrupted by subsequent m_pullup() or other mbuf m_*() operations.
I still believe that using MTAG is appropriate.
How about something like this? (not tested)
Wow, that
Hello,
On Tue, 15 Nov 2022 10:29:56 +
"Michael Lorenz" wrote:
> Module Name: src
> Committed By: macallan
> Date: Tue Nov 15 10:29:56 UTC 2022
>
> Modified Files:
> src/sys/kern: subr_pserialize.c
>
> Log Message:
> don't KASSERT(kpreempt_disabled()) while cold
>
>> > > This clearly is a layering/abstraction violation and would have been
>> > > good to discuss upfront.
>> > >
>> > > Where do you make use of that information? What about other packet
>> > > injection
>> > > paths?
>> >
>> > The next commit uses it in if_arp to ensure that the DaD probe
On Tue, Nov 15, 2022 at 11:29 AM Ryota Ozaki wrote:
>
> On Mon, Nov 14, 2022 at 8:52 PM Roy Marples wrote:
> >
> > On 14/11/2022 11:04, Martin Husemann wrote:
> > > This clearly is a layering/abstraction violation and would have been
> > > good to discuss upfront.
> > >
> > > Where do you make
On Mon, Nov 14, 2022 at 8:52 PM Roy Marples wrote:
>
> On 14/11/2022 11:04, Martin Husemann wrote:
> > This clearly is a layering/abstraction violation and would have been
> > good to discuss upfront.
> >
> > Where do you make use of that information? What about other packet injection
> > paths?
Hi,
Thank you for your updating.
Thanks,
On 2022/11/14 19:15, Roy Marples wrote:
On 14/11/2022 09:49, Kengo NAKAHARA wrote:
Hi,
Please update the size in comment, when struct pkthdr is changed.
https://github.com/NetBSD/src/blob/trunk/sys/sys/mbuf.h#L181
Thanks,
Done, thanks.
Roy
201 - 300 of 11235 matches
Mail list logo
