Re: Proposal: validate FFS root inode during the mount.

Kirk has added a bunch of checksum and other integrity checks to FreeBSD. If you are looking for extra sanity, that might be a good place to snag code from. They would be more comprehensive than just checking the root node... Warner On Wed, Nov 20, 2019, 8:39 AM Mouse wrote: > >>> To make sure

Re: Adding an ioctl to check for disklabel existence

On Thu, Oct 3, 2019 at 9:19 AM Robert Elz wrote: > Now it makes no sense at all. > FreeBSD made the explicit decision when disks were sneaking up on 2TB to move to GPT labels. Why invent a new scheme that interoperates poorly with other things? GPT, for better or worse, won. disklabel64 would

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

On Sat, Jun 29, 2019 at 2:04 PM Christos Zoulas wrote: > In article zccfacpsbmoz-4xguf54n...@mail.gmail.com>, > Andrew Cagney wrote: > > > >Having 32-bit and 64-bit debuggers isn't sufficient. Specifically, it > >can't handle an exec() call where the new executable has a different > >ISA;

Re: Removing PF

On Sun, Mar 31, 2019, 8:13 AM Sevan Janiyan wrote: > > > On 30/03/2019 23:27, Mouse wrote: > > (Rule of thumb: anyone who calls something "secure" or > > "insecure" without giving any indication of the threat model in > > question either doesn't understand security or hopes you don't; neither >

Re: Removing PF

On Sat, Mar 30, 2019, 2:29 PM Maxime Villard wrote: > Le 30/03/2019 à 20:26, Michael van Elst a écrit : > > On Sat, Mar 30, 2019 at 08:10:21PM +0100, Maxime Villard wrote: > > > >> ... sure, meanwhile you didn't really answer to the core of the issue, > which > >> I think was stated clearly by

Re: Regarding the ULTRIX and OSF1 compats

Picking a random message in this thread to respond to. FreeBSD has struggled with deprecation as well (which is what this is). I'm working on a doc to help there, but the basic criteria are: 1. What is the cost to keep it. Include the API change tax here. 2. What is the benefit the project gets

Re: nandemulator

On Sun, Feb 24, 2019, 11:33 AM David Holland wrote: > On Sat, Feb 23, 2019 at 02:05:39PM -0700, Warner Losh wrote: > > On Sat, Feb 23, 2019 at 12:40 PM David Holland < > dholland-t...@netbsd.org> > > wrote: > > > > > Do we have docs

Re: nandemulator

On Sat, Feb 23, 2019 at 12:40 PM David Holland wrote: > Do we have docs for the object nandemulator is supposed to be > emulating? Some questions have arisen about how complete it is and > nobody I've talked to seems to really have answers. > So looking at the code... It's an ONFI emulator.

Re: scsipi: physio split the request

On Fri, Dec 28, 2018, 11:04 AM Warner Losh > > On Fri, Dec 28, 2018, 1:25 AM matthew green >> > Of course larger transfers would also mitigate the overhead for each I/O >> > operation, but we already do several Gigabyte/s with 64k transfers and >> > filesy

Re: scsipi: physio split the request

On Fri, Dec 28, 2018, 1:25 AM matthew green > Of course larger transfers would also mitigate the overhead for each I/O > > operation, but we already do several Gigabyte/s with 64k transfers and > > filesystem I/O tends to be even smaller. > > yes - the benefits will be in the 0-10% range for most

Re: svr4, again

On Thu, Dec 20, 2018, 6:17 PM Maxime Villard Le 20/12/2018 à 18:11, Kamil Rytarowski a écrit : > > https://github.com/krytarowski/franz-lisp-netbsd-0.9-i386 > > > > On the other hand unless we need it for bootloaders, drivers or > > something needed to run NetBSD, I'm for removal of srv3, sunos

Re: svr4, again

On Wed, Dec 19, 2018 at 4:38 PM wrote: > On Wed, Dec 19, 2018 at 11:01:27AM -0700, Warner Losh wrote: > > FreeBSD ditched SYSV maybe 2 years ago, but > > we still have IBCS in the tree because people are still using it (last we > > checked) and bug fixes / report

Re: Support for tv_sec=-1 (one second before the epoch) timestamps?

On Sat, Dec 15, 2018, 1:17 PM Mouse > Might I suggest that the obvious solution to this, and probably a > > host of other issues, is to make time_t an always negative number > > (negint/neglong?) and redefine the epoch as 03:14:09 UTC on Tuesday, > > 19 January 2038, > > While it's academic as

Re: Support for tv_sec=-1 (one second before the epoch) timestamps?

On Thu, Dec 13, 2018, 9:41 AM > > > On Dec 13, 2018, at 6:06 AM, Martin Husemann wrote: > > > > > > [EXTERNAL EMAIL] > > > > On Thu, Dec 13, 2018 at 03:29:03AM +, David Holland wrote: > >> On Wed, Dec 12, 2018 at 10:27:04PM +0100, Joerg Sonnenberger wrote: > >>> On Wed, Dec 12, 2018 at

Re: Support for tv_sec=-1 (one second before the epoch) timestamps?

On Wed, Dec 12, 2018 at 2:34 PM Joerg Sonnenberger wrote: > On Wed, Dec 12, 2018 at 08:46:33PM +0100, Michał Górny wrote: > > While researching libc++ test failures, I've discovered that NetBSD > > suffers from the same issue as FreeBSD -- that is, both the userspace > > tooling and the kernel

Re: Missing compat_43 stuff for netbsd32?

On Tue, Sep 11, 2018, 5:48 PM Brad Spencer wrote: > Eduardo Horvath writes: > > > On Tue, 11 Sep 2018, Paul Goyette wrote: > > > >> While working on the compat code, I noticed that there are a few old > >> syscalls which are defined in syc/compat/netbsd323/syscalls.master > >> with a type of

Re: Missing compat_43 stuff for netbsd32?

On Tue, Sep 11, 2018, 4:38 PM Thor Lancelot Simon wrote: > There can be a lot of value to being able to run really old executables, > but you need the right customer in the right state of utter desperation... > I'm writing a COMPAT_V7 right now to celebrate Unix 50 next year. To be difficult,

Re: new errno ?

On Sat, Jul 7, 2018, 11:43 AM Jason Thorpe wrote: > > > On Jul 6, 2018, at 2:49 PM, Eitan Adler wrote: > > For those interested in some of the history: > https://lists.freebsd.org/pipermail/freebsd-hackers/2003-May/000791.html > > > ...and the subsequent thread went just as I expected it might.

Re: new errno ?

On Fri, Jul 6, 2018, 2:10 PM Greg Troxel wrote: > > Phil Nelson writes: > > > Hello, > > > > In working on the 802.11 refresh, I ran into a new errno code from > FreeBSD: > > > > #define EDOOFUS 88 /* Programming error */ > > > > Shall we add this one? (Most likely

Re: QEMU/NetBSD status wiki page

On Sun, May 27, 2018 at 11:57 AM, Kamil Rytarowski <n...@gmx.com> wrote: > On 27.05.2018 16:53, Warner Losh wrote: > > > > > > On Sun, May 27, 2018 at 4:05 AM, Kamil Rytarowski <n...@gmx.com > > <mailto:n...@gmx.com>> wrote: > > > >

Re: QEMU/NetBSD status wiki page

On Sun, May 27, 2018 at 4:05 AM, Kamil Rytarowski wrote: > As requested, I've prepared a QEMU/NetBSD status page: > > http://wiki.netbsd.org/users/kamil/qemu/ > > I've attempted to be rather conservative with claims that something > works, without detailed verification. > FreeBSD

Re: Kernel module framework status?

On Sat, May 5, 2018, 4:17 AM wrote: > If someone wants to do this route of metadata, please consider the > addition of a metadata property "should this be auto loaded". > > Currently we have ad-hoc logic for some modules that might be auto > loaded (compat_...) and it'd probably

Re: Kernel module framework status?

On Fri, May 4, 2018 at 12:32 AM, John Nemeth wrote: > On May 3, 10:54pm, Mouse wrote: > } > } > There is also the idea of having a module specify the device(s) > } > it handles by vendor:product > } > } Isn't that rather restrictive in what buses it permits supporting? >

Re: Kernel module framework status?

On Thu, May 3, 2018 at 8:54 PM, Mouse wrote: > > There is also the idea of having a module specify the device(s) > > it handles by vendor:product > > Isn't that rather restrictive in what buses it permits supporting? > > Indeed, PCI (and close relatives, like

Re: Spectre

On Thu, Jan 18, 2018 at 7:58 AM, wrote: > > > > On Jan 18, 2018, at 9:48 AM, Mouse wrote: > > > >> Since this involves a speculative load that is legal from the > >> hardware definition point of view (the load is done by kernel code), > >> this

Re: virtual to physical memory address translation

On Mon, Jan 15, 2018 at 8:09 AM, John Nemeth wrote: > On Jan 15, 2:04pm, Michael van Elst wrote: > } m...@netbsd.org (Emmanuel Dreyfus) writes: > } > } >Sorry if that has been covered ad nauseum, but I canot find relevant > } >information about that: on NetBSD, how can I get

Re: Reading a DDS tape with 2M blocks

On Jan 9, 2018 3:59 PM, "Greg Troxel" wrote: Edgar Fuß writes: > I have a DDS tape (written on an IRIX machine) with 2M blocks. > Any way to read this on a NetBSD machine? > My memories of SCSI ILI handling on DDS are fuzzy. I remember you can operate >

Re: Proposal to obsolete SYS_pipe

On Dec 24, 2017 11:10 PM, "Robert Elz" wrote: Date:Sun, 24 Dec 2017 18:42:19 -0800 From:John Nemeth Message-ID: <201712250242.vbp2gjjm017...@server.cornerstoneservice.ca> | HISTORY | A pipe() function call appeared in

Re: ext2fs superblock updates

On Thu, Nov 16, 2017 at 12:12 PM, Mouse wrote: > >> They are generated by _newfs_ and left untouched thereafter. > > Interesting, thanks. what's so useful about the superblock at newfs > > time? > > It contains enough information for fsck to find other critical

Re: FUA and TCQ

On Mon, Sep 26, 2016 at 8:27 AM, Michael van Elst <mlel...@serpens.de> wrote: > i...@bsdimp.com (Warner Losh) writes: > >>NVMe is even worse. There's one drive that w/o queueing I can barely >>get 1GB/s out of. With queueing and multiple requests I can get the >>

Re: Plan: journalling fixes for WAPBL

On Sat, Sep 24, 2016 at 2:01 AM, David Holland wrote: > On Fri, Sep 23, 2016 at 07:51:32PM +0200, Manuel Bouyer wrote: > > > > *if you have the write cache disabled* > > > > > > *Running with the write cache enabled is a bad idea* > > > > On ATA devices, you can't

Re: Plan: journalling fixes for WAPBL

On Fri, Sep 23, 2016 at 11:54 AM, Warner Losh <i...@bsdimp.com> wrote: > On Fri, Sep 23, 2016 at 11:20 AM, Thor Lancelot Simon <t...@panix.com> wrote: >> On Fri, Sep 23, 2016 at 05:15:16PM +, Eric Haszlakiewicz wrote: >>> On September 23, 2016 10:51:30 AM EDT

Re: Plan: journalling fixes for WAPBL

On Fri, Sep 23, 2016 at 11:20 AM, Thor Lancelot Simon <t...@panix.com> wrote: > On Fri, Sep 23, 2016 at 05:15:16PM +, Eric Haszlakiewicz wrote: >> On September 23, 2016 10:51:30 AM EDT, Warner Losh <i...@bsdimp.com> wrote: >> >All NCQ gives you is the ability

Re: FUA and TCQ

On Fri, Sep 23, 2016 at 8:05 AM, Thor Lancelot Simon wrote: > Our storage stack's inability to use tags with SATA targets is a huge > gating factor for performance with real workloads (the residual use of > the kernel lock at and below the bufq layer is another). FreeBSD's

Re: Plan: journalling fixes for WAPBL

On Fri, Sep 23, 2016 at 7:38 AM, Thor Lancelot Simon wrote: > On Fri, Sep 23, 2016 at 11:47:24AM +0200, Manuel Bouyer wrote: >> On Thu, Sep 22, 2016 at 09:33:18PM -0400, Thor Lancelot Simon wrote: >> > > AFAIK ordered tags only guarantees that the write will happen in order, >> >

Re: Proposal for kernel clock changes

On Apr 1, 2014, at 1:50 PM, David Laight da...@l8s.co.uk wrote: This may mean that you can (effectively) count the ticks on all your clocks since 'boot' and then scale the frequency of each to give the same 'time since boot' - even though that will slightly change the relationship between

Re: asymmetric smp

On Apr 1, 2014, at 5:49 AM, Johnny Billquist b...@softjar.se wrote: Good points. Is this the right time to ask why booting NetBSD on a VAX (a 3500) now takes more than 15 minutes? What is the system doing all that time??? FreeBSD used to take forever to boot on certain low-end ARM CPUs with

Re: hf/sf [Was Re: CVS commit: pkgsrc/misc/raspberrypi-userland]

On Nov 11, 2013, at 4:31 PM, Justin Cormack wrote: On Mon, Nov 11, 2013 at 10:56 PM, Michael van Elst mlel...@serpens.de wrote: m...@3am-software.com (Matt Thomas) writes: Exactly. with hf, floating point values are passed in floating point registers. That can not be hidden via a library

Re: MACHINE_ARCH on NetBSD/evbearmv6hf-el current

On Oct 26, 2013, at 12:24 PM, Alistair Crooks wrote: On Sat, Oct 26, 2013 at 11:10:52AM -0700, Matt Thomas wrote: On Oct 26, 2013, at 10:54 AM, Izumi Tsutsui tsut...@ceres.dti.ne.jp wrote: By static MACHINE_ARCH, or dynamic sysctl(3)? If dynamic sysctl(3) is prefered, which node?

Re: pulse-per-second API status

On Nov 1, 2013, at 12:19 PM, paul_kon...@dell.com wrote: On Nov 1, 2013, at 2:04 PM, Mouse mo...@rodents-montreal.org wrote: ... But it still may not work in the sense of living up to the expectations people have come to have for PPS on serial ports. My worry is not that it's not the

Re: NetBSD port for AT91SAM9G20?

On Sep 5, 2012, at 12:43 AM, Jukka Marin wrote: Hi, I have asked this before, but got no replies. We are making AT91SAM9G20 based hardware and I would love to run NetBSD on it. However, I can't find the time to port NetBSD to this MCU and hardware. Is there anyone with some spare time

Re: NetBSD port for AT91SAM9G20?

On Sep 5, 2012, at 11:50 AM, vinc...@labri.fr wrote: Warner Losh i...@bsdimp.com writes: On Sep 5, 2012, at 12:43 AM, Jukka Marin wrote: The main features of our current hardware are: - AT91SAM9G20 MCU (400 MHz) [...] Apart from a few clocks, this should work with the AT91SAM9260

Re: Path to kernel modules (second attempt)

On Jul 8, 2012, at 10:20 AM, Matthew Mondor wrote: On Sun, 8 Jul 2012 17:57:00 +0200 Edgar Fuß e...@math.uni-bonn.de wrote: Please not /kernel as it was already mentioned, it is too similar to /kern. What about /netbsd? E.g. /netbsd/6.0_BETA/{modules,kernel,firmware}.

Re: Path to kernel modules (second attempt)

On Jul 7, 2012, at 4:17 PM, Matthew Mondor wrote: On Sat, 07 Jul 2012 22:46:50 +0200 Jean-Yves Migeon jeanyves.mig...@free.fr wrote: On 07.07.2012 21:57, Mindaugas Rasiukevicius wrote: Hello, Regarding the PR/38724, I propose to change the path to /kernel/. Can we reach some consensus