Yes, the commit with log looks fine.
FWIW, I don't like the use of the word "legacy", essentially ever, but
especially not when the thing being dissed has not been well and truly
formally deprecated.
I am also befuddled with KERNEL_DIR being 'recent' and also '5 years
ago' but that's not about re
Taylor R Campbell writes:
>> Date: Fri, 20 Dec 2024 10:43:06 -0500
>> From: Greg Troxel
>>
>> I still am not clear on if having built packages like this as part of
>> build.sh, if using the system with normal native X and doing pkgsrc
>> builds later is goin
In that case it probably deserves a warning if build.sh is given -x, and
the comment expanded a bit. It makes sense now that you've explained,
but not something I'd expect random build.sh users to understand.
I still am not clear on if having built packages like this as part of
build.sh, if usin
Module Name:src
Committed By: gdt
Date: Sun Nov 3 14:00:52 UTC 2024
Modified Files:
src/external/cddl/osnet/dist/uts/common/fs/zfs: zvol.c
Log Message:
zvol: Implement DIOCCACHESYNC
Similarly to FreeBSD, simply call zil_commit when the DIOCCACHESYNC
ioctl is invoked on a
Module Name:src
Committed By: gdt
Date: Sun Nov 3 14:00:52 UTC 2024
Modified Files:
src/external/cddl/osnet/dist/uts/common/fs/zfs: zvol.c
Log Message:
zvol: Implement DIOCCACHESYNC
Similarly to FreeBSD, simply call zil_commit when the DIOCCACHESYNC
ioctl is invoked on a
Module Name:src
Committed By: gdt
Date: Fri Sep 20 22:45:15 UTC 2024
Modified Files:
src/lib/libm/src: s_remquo.c
Log Message:
libm/remquo: Fix bug where remquo returned wrong sign of quo
ISO C requires that quo be congruent to the quotient mod 2^k and have
a particular s
Module Name:src
Committed By: gdt
Date: Fri Sep 20 22:45:15 UTC 2024
Modified Files:
src/lib/libm/src: s_remquo.c
Log Message:
libm/remquo: Fix bug where remquo returned wrong sign of quo
ISO C requires that quo be congruent to the quotient mod 2^k and have
a particular s
Module Name:src
Committed By: gdt
Date: Fri Sep 20 18:08:33 UTC 2024
Modified Files:
src/lib/libm/src: s_remquo.c
Log Message:
libm/remquo: Fix bug where wrong quotient was returned
Fix taken from FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166463
htt
Module Name:src
Committed By: gdt
Date: Fri Sep 20 18:08:33 UTC 2024
Modified Files:
src/lib/libm/src: s_remquo.c
Log Message:
libm/remquo: Fix bug where wrong quotient was returned
Fix taken from FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166463
htt
Module Name:src
Committed By: gdt
Date: Thu Sep 19 19:43:13 UTC 2024
Modified Files:
src/distrib/sets/lists/debug: mi
src/distrib/sets/lists/tests: mi
src/tests/lib/libm: Makefile
Added Files:
src/tests/lib/libm: t_remquo.c
Log Message:
tests: Add t
9:43:13 gdt Exp $ */
+
+/*-
+ * Copyright (c) 2011 The NetBSD Foundation, Inc.
+ * All rights reserved.
+ *
+ * This code is derived from software contributed to The NetBSD Foundation
+ * by Jukka Ruohonen and Greg Troxel.
+ *
+ * Redistribution and use in source and binary forms, with or without
+
chris...@astron.com (Christos Zoulas) writes:
>>> POSIX.1-2024 removes asctime_r and ctime_r and does not let
>>> libraries define them, so remove them except when needed to
>>> conform to earlier POSIX. These functions are dangerous as they
>>> can overrun user buffers. If you s
Valery Ushakov writes:
> On Fri, Aug 16, 2024 at 19:06:15 +0900, Rin Okuyama wrote:
>
>> I've changed mknative-gdb to generate *.info by using makeinfo(1)
>> provided by pkgsrc-2024Q2:
>>
>> https://github.com/IIJ-NetBSD/netbsd-src/compare/master...rokuyama:netbsd-src:exp/mknative-gdb-makeinfo
>
Taylor R Campbell writes:
> How is the host C++ compiler supposed to know that we are asking it to
> compile C++11 and not C++98 or C++17?
The compilation line should pass --std=c++11. Arguably, any program
that invokes a compiler and does not pass a --std is buggy. Things only
mostly work bec
Module Name:src
Committed By: gdt
Date: Sat Oct 21 23:42:03 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig.8: Don't mention ciphertext
After all, this is not cgd(4).
To generate a diff of this commit:
cvs rdiff -u -r1.49 -r1.50 src/usr.
Module Name:src
Committed By: gdt
Date: Sat Oct 21 23:42:03 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig.8: Don't mention ciphertext
After all, this is not cgd(4).
To generate a diff of this commit:
cvs rdiff -u -r1.49 -r1.50 src/usr.
Module Name:src
Committed By: gdt
Date: Sat Oct 21 23:38:26 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig: Improve recent caching edit to man page
Explain that typical usage patterns don't run into consistency issues.
Xref the -i flag.
Module Name:src
Committed By: gdt
Date: Sat Oct 21 23:38:26 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig: Improve recent caching edit to man page
Explain that typical usage patterns don't run into consistency issues.
Xref the -i flag.
Module Name:src
Committed By: gdt
Date: Fri Oct 20 12:45:17 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig: Add caution to man page about cache bypassing behavior
To generate a diff of this commit:
cvs rdiff -u -r1.46 -r1.47 src/usr.sbin
Module Name:src
Committed By: gdt
Date: Fri Oct 20 12:45:17 UTC 2023
Modified Files:
src/usr.sbin/vnconfig: vnconfig.8
Log Message:
vnconfig: Add caution to man page about cache bypassing behavior
To generate a diff of this commit:
cvs rdiff -u -r1.46 -r1.47 src/usr.sbin
Module Name:src
Committed By: gdt
Date: Mon Aug 14 13:54:05 UTC 2023
Modified Files:
src/distrib/amd64/installimage: installimage.mk
Log Message:
amd64 installimage: Reduce non-xz size slightly to fit 4GB flash drives
The installimage sizes were bumped in 2022 because of
Module Name:src
Committed By: gdt
Date: Mon Aug 14 13:54:05 UTC 2023
Modified Files:
src/distrib/amd64/installimage: installimage.mk
Log Message:
amd64 installimage: Reduce non-xz size slightly to fit 4GB flash drives
The installimage sizes were bumped in 2022 because of
Module Name:src
Committed By: gdt
Date: Sat Jul 29 23:11:51 UTC 2023
Modified Files:
src/share/man/man4: nvmm.4
Log Message:
nvmm(4): Document that VMX Unrestricted Guest is required
To generate a diff of this commit:
cvs rdiff -u -r1.6 -r1.7 src/share/man/man4/nvmm.4
P
Module Name:src
Committed By: gdt
Date: Sat Jul 29 23:11:51 UTC 2023
Modified Files:
src/share/man/man4: nvmm.4
Log Message:
nvmm(4): Document that VMX Unrestricted Guest is required
To generate a diff of this commit:
cvs rdiff -u -r1.6 -r1.7 src/share/man/man4/nvmm.4
P
Taylor R Campbell writes:
> Well, what happened is:
>
> 1. I was drafting posix_memalign and aligned_alloc for libbsdmalloc in
>response to the thread about static program size yesterday, and
>carefully reading the specs -- POSIX 2018, C11 -- to make sure I
>got all the details right.
Emmanuel Dreyfus writes:
> On Thu, Jun 29, 2023 at 08:43:36PM -0400, Greg Troxel wrote:
>> > Primary bootstrap is now able to read a GPT inside RAIDframe.
>> did you also update documentation?
>
> We do not have any documentation specific to primary bootstrap.
> x86/b
"Emmanuel Dreyfus" writes:
> Log Message:
> Primary bootstrap is now able to read a GPT inside RAIDframe.
did you also update documentation?
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 wha
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
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 ac
"David H. Gutteridge" writes:
Thanks for the history and it is all sensible.
> "nul-terminated" and "null-terminated" seemed more common in man pages
> that originated from historical BSD sources, so, lacking any style
> guide, I inferred the lowercase "nul" was more "correct" as "BSD style"
>
Taylor R Campbell writes:
>> Date: Sat, 26 Mar 2022 16:53:19 +0100
>> From: Roland Illig
>>
>> The term "null-terminated string" is quite common when talking about C.
>> In contrast, the word "nul" in "nul-terminated" always reminds me of
>> the character abbreviation in ASCII, which has a n
Brad Spencer writes:
> What is referred to here is a specific ZFS idea and should not be
> confused with any sort of global notion. Specifically, ZFS, by default
> and in common use, does not use anything like a /etc/fstab or
> /etc/vfstab to specify where the filesets get mounted. It also doe
I apologize for failing to understand "zfs legacy mount" and incorrectly
associating it with how I usually encounter the word legacy.
I now understand that you meant to separate:
zfs's preferred path of having mountpoints stored as volume
properties, which is a different way of specifying wh
Simon Burge writes:
> I'm running with a complete ZFS-only setup with no legacy mounts. This
> is my basic ZFS layout (leaving out a few mounts that don't add any more
> value to this discussion):
>
> NAME MOUNTPOINT
> pool0 /pool0
>
matthew green writes:
> could this be done with include and "no foo" statement?
> eg, like sys/arch/sparc/conf/INSTALL does.
Maybe, but I'm not sure it will end up working. Right now we don't know
if any of the missing things will be trouble, and even if we do move to
include/no I'd like to do
Jason Thorpe writes:
>> On Jun 16, 2020, at 8:43 AM, Martin Husemann wrote:
>>
>> No, that is definitively not OK, which is what the PR is about.
>>
>> It is not OK for a regular atf run to cause a reboot of the test machine
>> though, so this is a temporary hack around the issue (and admitedl
Great to hear of progress.
I don't see why we don't care about 8. Given our release policy, that
is supported until 10 is released.
Generally speaking divergence with upstream is a problem and we lost
these changes anyway in pkgsrc and every standalone GNU toolchain copy.
Agreed that divergence is a problem, but so is having bugs. It's a
question of the right balance in each case.
Finding a creative way to make this at
Greg Troxel writes:
> It seem really obvious to me, and obvious that it is netbsd consensus,
> that a tool that needs tmp (without needing persistence) should default
> to /tmp. So I think it's unreasonable to follow upstream here, and
> unreasonable to ask everybody to ei
Kamil Rytarowski writes:
> On 26.03.2020 15:01, Martin Husemann wrote:
>> On Thu, Mar 26, 2020 at 02:57:40PM +0100, Kamil Rytarowski wrote:
>>> The build of tools could be fixed independently.
>> The problem is that we build the whole system with the tools gcc, and that
>> gcc misbehaves (or so I
Taylor R Campbell writes:
>> Do we insist on this patch? Can we remove it from local sources?
>
> We should keep the change. There is no semantic justification for
> putting build-time temporary files in the directory for temporary
> files that are meant to persist across reboot. These temporar
J. Hannken-Illjes writes:
>> Forgot to add in the commit log, the changes have been pulled in from
>> upstream openzfs.
>>
>> https://github.com/openzfs/zfs/commit/928e8ad47d3478a3d5d01f0dd6ae74a9371af65e#diff-9fd6b453f8153161abe0728c449e6505R4386
>
> This is NOT our upstream --
This seems to b
Warner Losh writes:
> Just a quick note: when FreeBSD when from 9 to 10, we had to play 'hunt the
> wumpus' for all the autoconfig scripts that suddenly thought they were
> configuring for FreeBSD 1.0.
>
> If you can arrange it, it might make sense to do a pkgsrc run on an
> experimental system t
Martin Husemann writes:
> On Mon, Dec 23, 2019 at 09:02:50AM -0500, Greg Troxel wrote:
>> Well, we are coming up on a year since netbsd-9 was branched, or at
>> least will arrive there before this discussion resolves. So cutting
>> -10 before we hit 100 works for me :-)
Kamil Rytarowski writes:
> On 23.12.2019 01:54, Roy Marples wrote:
>> On 22/12/2019 22:24, Andrew Doran wrote:
>>> NetBSD 9.99.29 - struct mount changed.
>>
>> Just curious - does our build software cope with 3 digit for the last
>> number?
>>
>> Roy
>
> At least from the __NetBSD_Version__ poi
David Brownlee writes:
> On Thu, 14 Nov 2019 at 21:05, Christos Zoulas wrote:
>>
>> The first issue is that I prefer to have tar respect existing
>> symlinks (ones that it did not create by default -- without having
>> to specify extra flags) since to do this (in my opinion) does not
>> pose a s
m...@netbsd.org writes:
> These seem to be lowercase versions of the same names. We're going to
> have trouble with the people who use case insensitive filesystems and
> CVS.
With any luck the multicase stuff is just dups to prune and not useful.
> (Or maybe it's not so bad because they're file
Martin Husemann writes:
> On Thu, Aug 08, 2019 at 08:09:19PM -0400, Greg Troxel wrote:
>> In addition, I don't like it that images have stuff in /boot in the DOS
>> partition that can't be found in some obvious place, like /usr/mdec.
>> But I haven't gotten ar
Andreas Gustafsson writes:
> I really don't like the general idea of introducing differences
> between images and systems installed through sysinst. It's confusing
> for users, and also means that testing of one is less likely to apply
> to the other.
Agreed strongly.
In addition, I don't like
Module Name:src
Committed By: gdt
Date: Mon Jul 29 17:53:20 UTC 2019
Modified Files:
src/etc: MAKEDEV.tmpl
Log Message:
MAKEDEV.tmpl: Create nodes for 16 USB hubs
As proposed on current-users, but with better formatting.
To generate a diff of this commit:
cvs rdiff -u -
Module Name:src
Committed By: gdt
Date: Mon Jul 29 17:53:20 UTC 2019
Modified Files:
src/etc: MAKEDEV.tmpl
Log Message:
MAKEDEV.tmpl: Create nodes for 16 USB hubs
As proposed on current-users, but with better formatting.
To generate a diff of this commit:
cvs rdiff -u -
Module Name:src
Committed By: gdt
Date: Mon Jul 29 12:07:57 UTC 2019
Modified Files:
src/sys/dev/ic: mfi.c
Log Message:
sys/dev/ic/mfi.c: Add missing break in switch
(The entire switch is guarded by MFI_DEBUG and is known not to build.)
Reported by Oskar.
To generate a
Module Name:src
Committed By: gdt
Date: Mon Jul 29 12:07:57 UTC 2019
Modified Files:
src/sys/dev/ic: mfi.c
Log Message:
sys/dev/ic/mfi.c: Add missing break in switch
(The entire switch is guarded by MFI_DEBUG and is known not to build.)
Reported by Oskar.
To generate a
Thomas Klausner writes:
> P.S.: The file is 44k, so I'm not convinced by the "/ is small"
> argument. ;)
100 * 44k is 4400k :-) The / and /usr distinction is longstanding, I
don't think we should give up on it easily.
Ryota Ozaki writes:
>> And, if someone is inclined, having better checks with meaurable
>> slowdown under DEBUG sounds ok too, but my revised understanding is
>> unclear on whether that's helpful. (But I am only trying to keep
>> performance under DIAGNOSTIC high; I am unconcerned about DEBUG an
Ryota Ozaki writes:
> On Tue, May 14, 2019 at 2:31 AM Jason Thorpe wrote:
>>
>>
>>
>> > On May 13, 2019, at 7:17 AM, Greg Troxel wrote:
>> >
>> > 2) Your option 2 seems to involve two things at once:
>> >
>> > - migration
Ryota Ozaki writes:
> On Sat, May 11, 2019 at 10:49 AM Greg Troxel wrote:
>> >> I'm sorry for delaying this task. Finally I have benchmarked a revised
>> >> patch
>> >> (our benchmarking setups have been out of service for a couple of
>> &g
Kamil Rytarowski writes:
> On 08.05.2019 11:34, Ryota Ozaki wrote:
>> On Sat, Apr 20, 2019 at 6:45 PM Ryota Ozaki wrote:
>>>
>>> On Fri, Apr 19, 2019 at 6:49 PM Kamil Rytarowski wrote:
On 19.04.2019 11:41, J. Hannken-Illjes wrote:
>> On 19. Apr 2019, at 03:52, Ryota Ozaki wrote:
matthew green writes:
> (i wouldn't pick 'wheel' as this group -- i would invent a
> new group either called 'net' or 'wpa', with no underscore
> since they're designed to be assigned, unlike the groups
> for specific programs security models.)
Are you saying that you are ok with the following:
Jason Thorpe writes:
>> On Jan 13, 2019, at 5:21 AM, Greg Troxel wrote:
>>
>> Even if you have to be root, these changes are still hugely useful.
>> "sudo wpa_cli" is not that hard, even if it seems like it should not be
>> necessary.
>
> ...but
Roy Marples writes:
> On 13/01/2019 10:20, matthew green wrote:
>> shouldn't one need to be root to modify network configuration?
>> i shouldn't be able to tell wpa_supplicant to do something as
>> non-root, in a default install.
>
> In a default install the only member of wheel is root and
> wpa
matthew green writes:
>> In short, this is because -munaligned-access is enabled on ARMv6+ by
>> default for GCC. As the unaligned memory access is forbidden in the
>> supervisor mode unlike in the user mode, we need to explicitly specify
>> -mno-unaligned-access for kernel on ARMv6+.
>
> i think
matthew green writes:
> Nick Hudson writes:
>> On 13/11/2018 08:21, matthew green wrote:
>> >> Modified Files:
>> >> src/sys/arch/evbarm/conf: std.generic64
>> >>
>> >> Log Message:
>> >> turn on MODULAR by default on aarch64
>> >
>> > optional things should not be in "std.foo". that should b
Greg Troxel writes:
> "Herbert J. Skuhra" writes:
>
>> On Sun, 04 Nov 2018 22:41:12 +0100, "Nick Hudson" wrote:
>>>
>>> Module Name:src
>>> Committed By: skrll
>>> Date: Sun Nov 4 21:41:12 UTC 20
"Herbert J. Skuhra" writes:
> On Sun, 04 Nov 2018 22:41:12 +0100, "Nick Hudson" wrote:
>>
>> Module Name: src
>> Committed By:skrll
>> Date:Sun Nov 4 21:41:12 UTC 2018
>>
>> Modified Files:
>> src/etc/etc.evbarm: Makefile.inc
>>
>> Log Message:
>> Only add GENERIC
m...@netbsd.org writes:
> On Sun, Apr 08, 2018 at 04:57:07PM +, Jared D. McNeill wrote:
>> @@ -82,6 +82,10 @@ The licenses currently used are:
>> mpl Mozilla Public license.
>> https://opensource.org/licenses/MPL-2.0
>>
>> +nvidia-firmware NVIDIA fir
Manuel Bouyer writes:
> On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
>> > Actually I did suggest to make the default dependant on MODULAR.
>>
>> what's the point exactly?
>
> that if I build a non-modular kernel with an emulation option explicitely
> selected, it works at boo
Nick Hudson writes:
> On 09/10/16 16:46, Jonathan A. Kollasch wrote:
>> Module Name: src
>> Committed By:jakllsch
>> Date:Sat Sep 10 15:46:36 UTC 2016
>>
>> Modified Files:
>> src/sys/dev/usb: usbdevices.config
>>
>> Log Message:
>> Make usscanner(4) useful by also a
David Holland writes:
> Well, it treats "this Sunday" as 6 days away. It apparently thinks
> "this X" is in the next seven days and "next X" is the week past that.
>
> That is not entirely crazy, though it's not really consistent with the
> conventional usage I know... but that usage isn't well
"David A. Holland" writes:
> Module Name: src
> Committed By: dholland
> Date: Thu Dec 31 10:18:00 UTC 2015
>
> Modified Files:
> src/tests/lib/libutil: t_parsedate.c
>
> Log Message:
> When evaluated on a Sunday, "next Sunday" means 7 days in the future,
> not 14. When evaluated
chris...@astron.com (Christos Zoulas) writes:
> In article <20151210081103.e0fbbf...@cvs.netbsd.org>,
> Kengo NAKAHARA wrote:
>>-=-=-=-=-=-
>>
>>Module Name: src
>>Committed By: knakahara
>>Date: Thu Dec 10 08:11:03 UTC 2015
>>
>>Modified Files:
>> src/sys/net: if_gif.c
>>
>>Log Me
chris...@zoulas.com (Christos Zoulas) writes:
> On Sep 25, 9:30am, m...@eterna.com.au (matthew green) wrote:
> -- Subject: re: CVS commit: src/external/cddl/osnet/dist/lib/libdtrace/common
>
> | when you sync things, can you also include what version you sunc with?
> | so for the next person to
"Michael van Elst" writes:
> Modified Files:
> src/sys/dev: dksubr.c
>
> Log Message:
> warn about labels only when built with DIAGNOSTIC
This feels like an abuse of DIAGNOSTIC, which is supposed to be about
asserts for detecting internal inconsistencies, not changing the
behavior of how
Joerg Sonnenberger writes:
> On Sun, Apr 26, 2015 at 10:07:32AM -0400, Greg Troxel wrote:
>> A broken build is evidence that the prior commits were not tested,
>> and thus need fixing. Objecting to fixing the build without testing
>> should be a far lower priority than
Izumi Tsutsui writes:
> joerg@ wrote:
>
>> > "Please don't commit untested and broken fix."
>> > "Please file a PR instead if you can't test it."
>>
>> I agree with Christos that leaving the build broken is worse. The
>> alternative band aids are much more involved, too. That shouldn't stop
>>
"S.P.Zeidler" writes:
> Thus wrote Paul Goyette (p...@vps1.whooppee.com):
>
>> At the very les, if we're going to have these acronyms, they should be
>> listed in a separate file which is not searched by default. Similar to what
>> is done with fortune(6).
>
> But that might not serve to indica
David Laight writes:
>> I'm also not sure we need a new kernel config. It seems the systems of
>> interest are limited to 486 machines without PCI (and thus EISA
>> probably), and that's a pretty narrow window around 1993-1994. So
>> leaving the lines commented out with a comment explaining it
Alan Barrett writes:
> On Sat, 07 Mar 2015, Martin Husemann wrote:
>> Anything that has no PCI.
>
> Could we rename LEGACY to something more descriptive? The problem
> with the name "LEGACY" is that it leaves people wondering whether or
> not particular hardware is old enough to be classified a
Martin Husemann writes:
> On Sat, Mar 07, 2015 at 08:13:17AM -0500, Greg Troxel wrote:
>> Will LEGACY be built by default?
>
> I would vote "no" on that one.
>
>> What's the set of computers that one has to use LEGACY on?
>
> Anything that has
Manuel Bouyer writes:
> On Sat, Mar 07, 2015 at 07:28:37AM +, matthew green wrote:
>> Module Name: src
>> Committed By:mrg
>> Date:Sat Mar 7 07:28:37 UTC 2015
>>
>> Modified Files:
>> src/distrib/notes/i386: contents
>> src/etc/etc.i386: Makefile.inc
>>
Marc Balmer writes:
> I think you contradict yourself, when you say a) new programs in base
> are pretty rare, and b) we have too much "commit first, argue about
> appropriate later".
Both are true; some/most "commit first discuss later" isn't about new
programs.
> While in some cases it makes
Marc Balmer writes:
>> I meant that adding to base was discuss-worthy because there's a
>> "bloat or necessary" question, not because of risk of breakage.
>
> Sure. So how much "bloat" is pwait? Is it a huge piece of software
> or a small utility? I think that matters a bit.
Posting a note t
Marc Balmer writes:
> Am 03.03.15 um 14:35 schrieb Greg Troxel:
>>
>> chris...@astron.com (Christos Zoulas) writes:
>>
>>> If we want to make every single change to go through
>>> tech-userlevel, we should institute a rule to do so. To my
>>
chris...@astron.com (Christos Zoulas) writes:
> If we want to make every single change to go through tech-userlevel,
> we should institute a rule to do so. To my knowledge we don't have yet
> such a rule. We already have the rest of the p* programs which originated
> in Solaris, we were missing t
Martin Husemann writes:
> On Mon, Jan 12, 2015 at 02:14:17PM -0500, Christos Zoulas wrote:
>> macppc? I don't think that the iso image produced there is bootable.
>> The question is how many of those images are bootable?
>
> Ma68k and macppc need "hybrid" HFS+/ISO9660 images, which mkimage can
>
Nick Hudson writes:
> On 07/25/14 17:13, Greg Troxel wrote:
>> Module Name: src
>> Committed By:gdt
>> Date:Fri Jul 25 16:13:21 UTC 2014
>>
>> Modified Files:
>> src/share/man/man4: ucom.4
>> src/sys/dev/usb: ucom.c
Erik Fair writes:
> On Apr 12, 2014, at 05:24, Greg Troxel wrote:
>
>> Module Name: src
>> Committed By:gdt
>> Date:Sat Apr 12 12:24:50 UTC 2014
>>
>> Modified Files:
>> src/sys/netinet: if_arp.c
>>
>> Log Me
Alan Barrett writes:
> On Wed, 09 Apr 2014, Thor Lancelot Simon wrote:
>>Modified Files:
>> src/distrib/utils/sysinst [tls-earlyentropy]: util.c
>>
>>Log Message:
>>Try to persistently gather some entropy at install time, to give the
>>fresh system a better chance of not doing awful things
chris...@zoulas.com (Christos Zoulas) writes:
> On Apr 3, 7:57am, m...@eterna.com.au (matthew green) wrote:
> -- Subject: re: CVS commit: src/sys/dev/raidframe
>
> | kernel configuration changes are not solutions, so 2 and 3 are out.
> |
> | if we do 4, we should instead add an option to mark
:33am, g...@ir.bbn.com (Greg Troxel) wrote:
> -- Subject: Re: CVS commit: src/sys/dev/raidframe
>
> | It seems there are 3 behaviors for root
> |
> | 1) don't change the root device (old behavior with -A yes)
>
> That does autoconfig for raid and does not deal with root at
I seemed to have missed the discussion for this change.
It seems there are 3 behaviors for root
1) don't change the root device (old behavior with -A yes)
2) if root is on a component, change root to the raid, otherwise don't
change.
3) force the root device to be the raid (old behavio
John Nemeth writes:
> On Mar 15, 1:50pm, "Jonathan A. Kollasch" wrote:
> }
> } Module Name:src
> } Committed By: jakllsch
> } Date: Sat Mar 15 13:50:01 UTC 2014
> }
> } Modified Files:
> } src/sys/arch/amd64/conf: XEN3_DOMU
> }
> } Log Message:
> } Enable PCI
John Nemeth writes:
> On Mar 15, 1:50pm, "Jonathan A. Kollasch" wrote:
> }
> } Module Name:src
> } Committed By: jakllsch
> } Date: Sat Mar 15 13:50:01 UTC 2014
> }
> } Modified Files:
> } src/sys/arch/amd64/conf: XEN3_DOMU
> }
> } Log Message:
> } Enable PCI
Paul Goyette writes:
> Me, too. But I'd rather that we had the equivalent ISCLR() macro, too,
> to remove another negation/complement.
So is ISCLR when passed two bits true if both are clear, or if it's just
not the case that both are set?
Arguably this points out that the ISSET docs should ex
Taylor R Campbell writes:
>Date: Wed, 12 Mar 2014 16:16:32 +0200
>From: Jukka Ruohonen
>
>On Wed, Mar 12, 2014 at 09:39:23AM +, Juergen Hannken-Illjes wrote:
>> Restructure layer_lock() to always lock before testing for dead node.
>> Use ISSET() to test flags, add assert
chris...@zoulas.com (Christos Zoulas) writes:
> On Jan 22, 7:29am, m...@3am-software.com (Matt Thomas) wrote:
> -- Subject: Re: CVS commit: src/share/mk
>
> | I always wondered why we don't use ln -sf=20
> | and avoid the race.
>
> That does not work because if the destnation is a directory it w
Alan Barrett writes:
> If you have "restrict default nopeer noquery" (the uncommented line in
> my commit), then time service will still work, but the configured
> servers will be denied query permission.
>
> If you use "restrict default ignore", then time service does not work.
I have found th
Alan Barrett writes:
> On Tue, 06 Aug 2013, Christos Zoulas wrote:
>>Module Name: src
>>Committed By: christos
>>Date: Tue Aug 6 05:42:43 UTC 2013
>>
>>Modified Files:
>> src/bin/csh: lex.c
>>
>>Log Message:
>>CID 1060854: Wrong sizeof argument (SIZEOF_MISMATCH)
>
> Does everybody
Erik Fair writes:
> On Jul 19, 2013, at 03:34, "Roy Marples" wrote:
>
>> Module Name: src
>> Committed By:roy
>> Date:Fri Jul 19 10:34:51 UTC 2013
>>
>> Modified Files:
>> src/bin/hostname: hostname.1 hostname.c
>>
>> Log Message:
>> Add the following options
>> -
1 - 100 of 124 matches
Mail list logo
