Re: Some guidance/suggestion please

On Jan 14, 9:11, Paul Goyette wrote: } } I'm looking into more modularization of the kernel, and my next } "target" is the ALTQ stuff. Right now, there are several network } device drivers that are built as loadable modules, yet they still } depend on conditional compilation. In particular,

Re: eventfd(2) and timerfd(2) APIs

On Sep 18, 10:26, Jason Thorpe wrote: } } Last year, I wrote implementations of the Linux eventfd(2) and } timerfd(2) interfaces for NetBSD, with the goal of improving our } Linux emulation. In order to be able to test them with ATF tests, } I went ahead and made them native calls as well. } }

Re: Devices.

On May 30, 14:24, Michael van Elst wrote: } mueller6...@twc.com ("Thomas Mueller") writes: } } > Where do I find the "enough dk* nodes" mode? Would it be in } > the kernel config? I never saw it. } } You can run devpubd. When a wedge and thus the dk* unit attaches, it } runs the 01-makedev

Re: Devices.

On May 29, 22:52, David Holland wrote: } On Sat, May 29, 2021 at 05:41:38PM -0400, Mouse wrote: } } > > For disks, which for historical reasons live in both cdevsw and } > > bdevsw, both entries would point at the same disk_dev. } > } > I would suggest getting rid of the bdev/cdev

Re: regarding the changes to kernel entropy gathering

On Apr 4, 23:09, Taylor R Campbell wrote: } } > Date: Sun, 04 Apr 2021 12:58:09 -0700 } > From: "Greg A. Woods" } > References: } > <20210404094958.692f360...@jupiter.mumble.net> } > } > At Sun, 4 Apr 2021 09:49:58 +, Taylor R Campbell wrote: } > > } > > Your change _creates_ the lie

Re: regarding the changes to kernel entropy gathering

On Apr 4, 9:49, Taylor R Campbell wrote: } } What NetBSD-current is telling you on your Xen system, on a CPU } predating RDRAND/RDSEED, is the unfortunate truth that there is no } reliable source of entropy available in your system -- annoying, yes, } but when you talk about `matters so

Re: "Boot this kernel once" functionality? (amd64)

On Sep 24, 9:14am, Reinoud Zandijk wrote: } Subject: Re: "Boot this kernel once" functionality? (amd64) } On Wed, Sep 16, 2020 at 12:09:43PM +0200, Martin Husemann wrote: } > On Wed, Sep 16, 2020 at 12:05:26PM +0200, Anthony Mallet wrote: } > > I was also wondering if it would be possible to pass

Re: modules item #14 revisited

On Dec 7, 4:31pm, Christos Zoulas wrote: } On Dec 7, 8:55pm, a...@absd.org (David Brownlee) wrote: } } | Very much like this - would assume that modules.tgz goes away? I can't say I'm a fan of this. I would hope that it goes away once we get serious about having a stable KABI for

Re: racy acccess in kern_runq.c

On Dec 6, 5:22pm, Don Lee wrote: } } Writing Kernel code *requires* knowledge of what code is generated } sometimes. In my experience, there have been standard techniques, } like pragmas and insertions of assembly code to suppress this } sort of undesirable optimization. } } Don't those

Re: racy acccess in kern_runq.c

On Dec 6, 3:02pm, Jason Thorpe wrote: } > On Dec 6, 2019, at 11:44 AM, paul.kon...@dell.com wrote: } > } > For clean semantics, I like ALGOL; too bad it is no longer used } } There's just too much shouting in ALGOL. Are you perhaps thinking of COBOL, which is traditionally all upper case.

Re: Adding an ioctl to check for disklabel existence

On Oct 3, 2:42pm, Rhialto wrote: } On Wed 02 Oct 2019 at 19:40:01 -0700, John Nemeth wrote: } > Cloning disks always presents issues. However, gpt(8) has } > grown a "uuid" command to generate new UUIDs. This was primarily } > done to help with the cloning probl

Re: Adding an ioctl to check for disklabel existence

On Oct 2, 9:47pm, Mouse wrote: } } >> If _that_'s what you're concerned about, then just grow the relevant } >> fields (and, presumably, change the magic number). } > Any change to the label format or semantics would make it be a } > completely different object, no longer compatible with

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 30, 1:06pm, Michael van Elst wrote: } On Mon, Sep 30, 2019 at 12:37:38AM -0700, John Nemeth wrote: } } > BTW, modules.conf isn't read by the kernel, it's read by } > /etc/rc.d/modules. Putting anything in there that would have a } > lasting effect (i.e. parameters for autoloade

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 30, 7:10am, Michael van Elst wrote: } chris...@astron.com (Christos Zoulas) writes: } >In article <20190929090053.g...@homeworld.netbsd.org>, } > wrote: } >>On Sat, Sep 28, 2019 at 01:29:39AM -, Christos Zoulas wrote: } >>> + "compat_linux", } >>> + "compat_linux32", }

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 26, 7:40pm, Christos Zoulas wrote: } In article <390f4c81-bf1c-443f-f7a9-a379c46b7...@m00nbsd.net>, } Maxime Villard wrote: } >I recently made a big set of changes to fix many bugs and vulnerabilities in } >compat_linux and compat_linux32, the majority of which have a security impact }

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 26, 5:18pm, Maxime Villard wrote: } Le 26/09/2019 à 17:15, Manuel Bouyer a écrit : } > On Thu, Sep 26, 2019 at 05:10:01PM +0200, Maxime Villard wrote: } >> issues for a clearly marginal use case, and given the current general } > ^^^ } > } > This

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 26, 4:40pm, Maxime Villard wrote: } Le 26/09/2019 à 16:36, Manuel Bouyer a écrit : } > On Thu, Sep 26, 2019 at 04:29:52PM +0200, Maxime Villard wrote: } >> Le 26/09/2019 à 16:22, Mouse a écrit : } >> Keeping them enabled for the <1% users interested means keeping } >>

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 26, 3:51pm, Maxime Villard wrote: } Le 26/09/2019 à 15:06, Mouse a écrit : } >> [...] compat_linux and compat_linux32 [...] } > } >> Keeping them enabled for the <1% users interested means keeping } >> vulnerabilities for the >99% who don't use these features. } > } > Are the usage

Re: Proposal, again: Disable autoload of compat_xyz modules

On Sep 26, 10:17am, Maxime Villard wrote: } } I recently made a big set of changes to fix many bugs and vulnerabilities in } compat_linux and compat_linux32, the majority of which have a security impact } bigger than the Intel CPU bugs we hear about so much. These compat layers are } enabled by

Re: Regarding the ULTRIX and OSF1 compats

On Mar 15, 10:31pm, Michael Kronsteiner wrote: } } i have this discussion today aswell... considering 64/32bit machines. } if you want ultrix, install ultrix. if you want osf1/dec unix/tru64 } install that. being able to run ummm nearly 20 year old binaries... } well. if thats what you want be

Re: Regarding the ULTRIX and OSF1 compats

On Mar 10, 12:16pm, Maxime Villard wrote: } Le 10/03/2019 à 11:25, Björn Johannesson a écrit : } > } > COMPAT_ULTRIX (mips) works fine which I recently discovered after shuffling } > some disks and NetBSD8 mounted the ULTRIX disk as / } } This more likely means that it was an old UFS disk that

Re: svr4, again

On Mar 9, 6:38am, "Jonathan A. Kollasch" wrote: } On Sat, Mar 09, 2019 at 11:28:05AM +0100, Maxime Villard wrote: } > Re-reading this thread - which was initially about SVR4 but which diverged in } > all directions -, I see there were talks about retiring COMPAT_ULTRIX and } > COMPAT_OSF1,

Re: Reserve device major numbers for pkgsrc

On Feb 16, 11:25pm, Kamil Rytarowski wrote: } } We started to build and ship kernel modules through pkgsrc. This is a really good thing and is part of the reason why modules exist. } I would like to reserve 3 major numbers for the HAXM case from the base } pool of devices and prevent

Re: scsipi: physio split the request

On Dec 27, 6:49pm, Michael van Elst wrote: } m...@netbsd.org (Emmanuel Dreyfus) writes: } } >Is there a reason other than historical for NetBSD 64kB limit? } } It's a compromise. Some buffers are statically sized for MAXPHYS } and some ancient hardware cannot exceed 64k (or even less) DMA

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

On Dec 16, 1:20pm, Mouse wrote: } } >> Not sure about that, but I agree that we should not extend the range } >> of time_t (aka "seconds since the epoch") to negative values. } > I'm not sure why anyone thinks that ship didn't sail years ago. } } > % cal 6 1942 } } How is that relevant to

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

On Dec 14, 2:38pm, wrote: } > On Dec 14, 2018, at 9:30 AM, Joerg Sonnenberger wrote: } > On Thu, Dec 13, 2018 at 02:37:06AM +0100, Kamil Rytarowski wrote: } >> In real life it's often needed to store time_t pointing before the UNIX } >> epoch. } > } > Again, I quite disagree and believe that

Re: Things not referenced in kernel configs, but mentioned in files.*

On Nov 13, 7:33am, Jason Thorpe wrote: } > On Nov 13, 2018, at 7:15 AM, John Nemeth wrote: } > } > That's a different kind of unusable. :-) That puts it in } > the same camp as strip, where there may be functioning hardware, } > but you can't do anything wi

Re: Things not referenced in kernel configs, but mentioned in files.*

On Nov 13, 7:10am, Martin Husemann wrote: } On Mon, Nov 12, 2018 at 05:18:41PM -0800, John Nemeth wrote: } > Was the ISDN code usable? Something in the back of my mind is telling } > me that it wasn't and thus was just clutter. } } It was usable, but even here it is hard (impo

Re: Things not referenced in kernel configs, but mentioned in files.*

On Nov 12, 2:12pm, Jason Thorpe wrote: } > On Nov 12, 2018, at 1:59 PM, John Nemeth wrote: } > } On Nov 12, 1:16pm, Jason Thorpe wrote: } > } > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote: } > } > } > } > wbsio and wt also seems to fit in that category

Re: Things not referenced in kernel configs, but mentioned in files.*

On Nov 12, 1:16pm, Jason Thorpe wrote: } Subject: Re: Things not referenced in kernel configs, but mentioned in fil } > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote: } > } > wbsio and wt also seems to fit in that category. } } Isn't "wt" an ancient PC tape dri

Re: Things not referenced in kernel configs, but mentioned in files.*

On Nov 12, 3:38pm, co...@sdf.org wrote: } On Mon, Nov 12, 2018 at 10:23:26AM -0500, Greg Troxel wrote: } > co...@sdf.org writes: } > } > > This is an automatically generated list with some hand touchups, feel } > > free to do whatever with it. I only generated the output. } > > } > > ac100ic } >

Re: Missing compat_43 stuff for netbsd32?

On Sep 11, 6:38pm, Thor Lancelot Simon wrote: } On Tue, Sep 11, 2018 at 03:35:24PM +, Eduardo Horvath wrote: } > } > It's probably only useful for running ancient SunOS 4.x binaries, maybe } > Ultrix, Irix or OSF-1 depending on how closely they followed BSD 4.3. } } Actually, I think

Re: Kernel module framework status?

On May 5, 10:17am, m...@netbsd.org 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 be

Re: Kernel module framework status?

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? I suppose that other types of identifiers could be used. } Indeed, PCI (and

Re: Kernel module framework status?

On May 2, 9:48am, Anders Magnusson wrote: } } I'm trying to find some documentation of the status of the kernel } modules, but only finds some scattered postings. } What is done, what is left, are there any decision points etc...? Paul Goyette has been making great strides on modularising

Re: virtual to physical memory address translation

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 the physical memory } >address given a virtual memory address? This is to port the

Re: LVM and 4K sectors

On Jan 3, 8:59pm, Benny Siegert wrote: } } I am trying to set up LVM on a 4T hard drive that has 4096-byte } sectors. However: } } # gpt create sd0 } # gpt add sd0 } /dev/rsd0: Partition 1 added: 49f48d5a-b10e-11dc-b99b-0019d1879648 6 976754635 } # newfs /dev/rdk4 } /dev/rdk4: 3815447.8MB

Re: modstat and kaslr

On Dec 31, 5:11pm, Maxime Villard wrote: } } Here is a patch [1] that hides the addresses of the kernel modules when } 'modstat -k' is entered by an unprivileged user. The current behavior is } preserved for root. } } The addresses currently leaked cannot be used to reconstruct the layout of }

Re: Proposal to obsolete SYS_pipe

On Dec 24, 9:37pm, Mouse wrote: } } > http://netbsd.org/~kamil/patch-00039-obsolete-SYS_pipe.txt } } I see no pipe2(2), nor change from pipe(2) to pipe(3) (with an xref to } pipe2(2)), both of which, it seems to me, should be part of this. From:

Re: amd64: kernel aslr support

On Oct 5, 8:30pm, Thor Lancelot Simon wrote: } } > * The RNG is not really strong. Help in this area would be greatly } >appreciated. } } This is tricky mostly because once you start probing for hardware } devices or even CPU features, you're going to find yourself wanting } more and more

Re: attaching cpu via lapic

On Aug 19, 1:31am, "Cherry G. Mathew" wrote: } } I'm trying to improve the semantics around x86 lapic vs. cpu, with a } view to wedging in the concept of "vcpu"s. } } TLDR: please review this patch: } http://ftp.netbsd.org/pub/NetBSD/misc/cherry/tmp/attach-cpu-with-lapic.diff } } Essentially,

Re: Proposal: Disable autoload of compat_xyz modules

On Aug 3, 11:35am, m...@netbsd.org wrote: } On Thu, Aug 03, 2017 at 01:23:17AM +0200, Emmanuel Dreyfus wrote: } > Taylor R Campbell wrote: } > } > Once every compatibility module would not loaded by default, pehaps the } > compat_xxx module could be loaded

Re: Proposal: Disable autoload of compat_xyz modules

On Aug 3, 4:09pm, Emmanuel Dreyfus wrote: } Subject: Re: Proposal: Disable autoload of compat_xyz modules } wrote: } } > By the way, isn't that what happens in practice anyway? the only way to } > reach the COMPAT_OTHEROS code is to first exec a binary, which looks for } > an

Re: Proposal: Disable autoload of compat_xyz modules

On Aug 3, 10:07am, Maxime Villard wrote: } Le 02/08/2017 à 23:08, Joerg Sonnenberger a écrit : } > On Wed, Aug 02, 2017 at 08:52:15PM +0200, Maxime Villard wrote: } >> I disagree. The cost of doing a modload is low enough compared to the } >> configuration needed to use compat_linux. Just like

Re: Proposal: Disable autoload of compat_xyz modules

On Aug 2, 5:02pm, Martin Husemann wrote: } On Wed, Aug 02, 2017 at 07:56:50AM -0700, Brian Buhrow wrote: } > Hello. My feeling is that the cost of requiring a modload to use } > compat_linux and compat_linux32 is fine. My concern is that by taking it } > out of the GENERIC kernel

Re: nanosleep() for shorted than schedule slice

On Jul 2, 8:04pm, David Holland wrote: } Subject: Re: nanosleep() for shorted than schedule slice } On Sun, Jul 02, 2017 at 12:54:52PM +0200, Joerg Sonnenberger wrote: } > > I wonder if it would make sense for nanosleep(2) to check that requested } > > sleeping time is shorter than a schedule

Re: nanosleep() for shorted than schedule slice

On Jul 2, 8:41pm, m...@netbsd.org wrote: } On Sun, Jul 02, 2017 at 08:38:24PM +, m...@netbsd.org wrote: } > On Sun, Jul 02, 2017 at 01:16:15PM +, Christos Zoulas wrote: } > > The solution is to implement "tickless kernel". It is not that difficult. } > } > It looks like we are always

Re: nanosleep() for shorted than schedule slice

On Jul 2, 1:16pm, Christos Zoulas wrote: } In article <1n8j63y.1pcs0owrn6gcem%m...@netbsd.org>, } Emmanuel Dreyfus wrote: } > } >I just encountered a situation where PHP performance on NetBSD is rather } >weak compared to Linux or MacOS X. } > } >The code calls PHP's uniqid() a

Re: kernel aslr: someone interested?

On Mar 25, 10:17pm, Mouse wrote: } } > [ASLR] is just one more check mark in the exploit building tool. } } Yes and no. } } It increases the work required to exploit any putative bugs. It does } not make exploitation impossible, but that does not mean it's not worth } making it harder. "You

re: "Wire" definitions and __packed

On Oct 6, 3:01pm, matthew green wrote: } } > X86 doesn't have alignment restrictions. The platform } > practically lets you get away with murder, and thus is not useful } > as a test platform. } } FWIW, this hasn't been true since at least 1999 (SSE.) also, That only counts if

Re: "Wire" definitions and __packed

On Oct 5, 10:15pm, Roy Marples wrote: } On Wednesday 05 October 2016 17:10:28 Eduardo Horvath wrote: } > On Wed, 5 Oct 2016, Roy Marples wrote: } > > On 04/10/2016 23:06, Joerg Sonnenberger wrote: } > > > I'd like to addressing this by cutting down on the first set. For this } > > > purpose, I

Re: Changing the return value of xxx_attach() from void to int.

On Jul 10, 9:37pm, David Holland wrote: } On Sat, Jul 09, 2016 at 08:45:15PM -0700, John Nemeth wrote: } > } The substance of that reservation is that there's not much point doing } > } it without also taking the time to correct the behavior, i.e., back } > } out properly if someth

Re: Changing the return value of xxx_attach() from void to int.

On Jul 10, 2:39am, David Holland wrote: } On Sat, Jul 09, 2016 at 04:57:20PM -0700, John Nemeth wrote: } > A number of people have expressed reservation (bring up memories } > of device_t and how long that took to settle out) indicating that } > this should be done on

Re: Changing the return value of xxx_attach() from void to int.

On Jun 23, 7:40pm, Masanobu SAITOH wrote: } } As you know, the return value of device driver's attach function is void. } I've thought that we should change it to int for many years. I believe I'm } not the only person. I've been meaning to get back to this one for some time... }

Re: DTrace on Xen?

On Apr 9, 1:50am, Christos Zoulas wrote: } In article <20160409012248.ga27...@panix.com>, } Thor Lancelot Simon wrote: } >Next try: is DTrace (particularly FBT) expected to work on NetBSD/xen? } > } >I'm struggling to get some grasp on why I/O to SCSI disks uses *25X* more }

Re: Simplify bridge(4)

On Feb 12, 10:33am, Roy Marples wrote: } On 12/02/2016 08:34, Ryota Ozaki wrote: } > On Thu, Feb 11, 2016 at 3:17 AM, Mouse wrote: } >>> [J]ust wondering if we are going to see vether(4) anytime soon. } >> } >> How would this vether differ from the existing tap?

Re: Simplify bridge(4)

On Feb 10, 6:56pm, Ryota Ozaki wrote: } } Thanks to introducing softint-based if_input, } we can simplify bridge(4). } } - Remove spin mutexes } - They were needed because some code of bridge could run in } hardware interrupt context } - We now need only an adaptive mutex for each

Re: vnd.c 1.254

On Jan 18, 12:52am, Robert Elz wrote: } } Date:Sun, 17 Jan 2016 17:52:16 +0100 } From:Manuel Bouyer } Message-ID: <20160117165216.ga4...@asim.lip6.fr> } } | I don't understand that. If you run in /, you get the busy/free devices } | in

Re: vnd.c 1.254

On Jan 17, 5:52pm, Manuel Bouyer wrote: } On Sun, Jan 17, 2016 at 11:04:23PM +0700, Robert Elz wrote: } > Date:Sun, 17 Jan 2016 15:52:38 +0100 } > From:Manuel Bouyer } > Message-ID: <20160117145238.ga3...@asim.lip6.fr> } > } > | unless you

Re: vnd.c 1.254

On Jan 17, 11:04pm, Robert Elz wrote: } } Date:Sun, 17 Jan 2016 15:52:38 +0100 } From:Manuel Bouyer } Message-ID: <20160117145238.ga3...@asim.lip6.fr> } } | unless you run vnconfig in the chroot. } } And /dev in the chroot has the same vnds

Re: vnd.c 1.254

On Jan 17, 9:37pm, Robert Elz wrote: } } Date:Sun, 17 Jan 2016 14:49:23 +0100 } From:Manuel Bouyer } Message-ID: <20160117134923.ga2...@asim.lip6.fr> } } | I mean, vnconfig -l (without other arguments) has been showing available } |

Re: vnd.c 1.254

On Jan 18, 5:58am, Robert Elz wrote: } } Date:Sun, 17 Jan 2016 12:42:32 -0800 } From:John Nemeth <jnem...@cue.bc.ca> } } And from a later message } (<201601172101.u0hl11cv023...@server.cornerstoneservice.ca>) ... } } | The only place the Xen scri

Re: vnd.c 1.254

On Jan 18, 6:37am, Robert Elz wrote: } } Date:Sun, 17 Jan 2016 23:26:35 +0100 } From:Michael van Elst } Message-ID: <20160117222634.ga5...@serpens.de> } } | I'd rather have something that lists existing devices, allocates } | a fresh one and

Re: vnd.c 1.254

On Jan 17, 1:01pm, Robert Elz wrote: } } Date:Sat, 16 Jan 2016 23:27:51 +0100 } From:Manuel Bouyer } Message-ID: <20160116222751.ga2...@asim.lip6.fr> } } | Also, you don't address the problem that, as I understand it and if } | the code

Re: vnd.c 1.254

On Jan 16, 7:21pm, Manuel Bouyer wrote: } } what problem are you trying to solve with this commit to sys/dev/vnd.c ? } revision 1.251 } date: 2015/11/09 17:41:24; author: christos; state: Exp; lines: +3 -5 } Return ENXIO if the get ioctl exceeds the number of configured devices. } XXX:

Re: In-kernel units for block numbers, etc ...

On Nov 29, 10:38am, Michael van Elst wrote: } Subject: Re: In-kernel units for block numbers, etc ... } jnem...@cue.bc.ca (John Nemeth) writes: } } > On a side note, if the backend is just a file, why doesn't } >vnd(4) work with NFS? } } A quick test shows that it works with a NFS f

Re: In-kernel units for block numbers, etc ...

On Nov 29, 12:05am, Michael van Elst wrote: } k...@munnari.oz.au (Robert Elz) writes: } } >I havem't looked carefully yet, but does vnd have the RMW behaviour to } >allow an emulated small sector drive to exist on a big sector underlying. } } It doesn't need to, the backend is a file and you can

Re: In-kernel units for block numbers, etc ...

On Nov 27, 6:00am, Robert Elz wrote: } } Date:Fri, 27 Nov 2015 07:12:50 +1100 } From:matthew green } Message-ID: <18094.1448568...@splode.eterna.com.au> } } | FWIW, i "fixed" raidframe on 4K disks a few years back. } } Do we allow mirroring

Re: POSIX.1 semaphores vs message queues

On Nov 13, 6:34pm, Masao Uebayashi wrote: } On Mon, Nov 9, 2015 at 7:13 PM, John Nemeth <jnem...@cue.bc.ca> wrote: } > On Nov 9, 11:15am, Masao Uebayashi wrote: } > } On Mon, Nov 9, 2015 at 9:21 AM, Joerg Sonnenberger } > } <jo...@britannica.bec.de> wrote: } > } > On

Re: POSIX.1 semaphores vs message queues

On Nov 13, 7:46pm, Masao Uebayashi wrote: } On Fri, Nov 13, 2015 at 8:05 PM, John Nemeth <jnem...@cue.bc.ca> wrote: } > On Nov 13, 6:34pm, Masao Uebayashi wrote: } > } On Mon, Nov 9, 2015 at 7:13 PM, John Nemeth <jnem...@cue.bc.ca> wrote: } > } > On Nov 9, 11:15a

Re: POSIX.1 semaphores vs message queues

On Nov 9, 11:15am, Masao Uebayashi wrote: } On Mon, Nov 9, 2015 at 9:21 AM, Joerg Sonnenberger } wrote: } > On Mon, Nov 09, 2015 at 08:05:43AM +0800, Paul Goyette wrote: } >> Well, both EXEC_SCRIPT and COREDUMP are modularized, and they _are_ } >> optional. } > } > See

Re: POSIX.1 semaphores vs message queues

On Nov 8, 7:22am, Paul Goyette wrote: } On Sat, 7 Nov 2015, Joerg Sonnenberger wrote: } > On Sun, Nov 08, 2015 at 06:35:36AM +0800, Paul Goyette wrote: } >> On Sat, 7 Nov 2015, Joerg Sonnenberger wrote: } >>> On Sat, Nov 07, 2015 at 10:55:49AM +0800, Paul Goyette wrote: } I'd like to

Re: Choice of SAS controller

On Jul 16, 3:27pm, Edgar =?iso-8859-1?B?RnXf?= wrote: } } I have been using Areca RAID controllers for several years now and } I have been pretty happy with them. } Can you drop me a part number? } The intersection between devices supported by NetBSD and those actually } still available on

Re: mount_checkdirs

On Jul 9, 12:27am, Rhialto wrote: } On Mon 06 Jul 2015 at 09:58:59 +, David Holland wrote: } } Also it's occasionally useful to mount over things and leave a process } underneath, which this logic seems to complicate. } } If I read the code correctly, it looks for processes that have a

Re: Specification of BTINFO_CONSOLE value in bootinfo.h

On Jun 3, 9:36am, deco33...@yandex.com wrote: } } I was reading the boot code to make netbsd multiboot compliant. Uh, it already is, or should be. See sys/arch/i386/i386/multiboot.c. I'm not certain if that is used for amd64. But, if not, it would probably be the place to start. } What

Re: Specification of BTINFO_CONSOLE value in bootinfo.h

On Jun 3, 9:57am, deco33...@yandex.com wrote: } Thanks but, } } lookup_bootinfo(BTINFO_CONSOLE); - initiate the console. This stuff is related to the NetBSD native bootloader and has absolutely nothing to do with multiboot. }-- End of excerpt from deco33...@yandex.com

Re: disk driver interface

On Dec 29, 9:28pm, Christos Zoulas wrote: } On Dec 29, 4:11pm, jnem...@cue.bc.ca (John Nemeth) wrote: } } | A semi-quick look around shows that pretty much everything } | that would support the drvctl(4) method would also support the } | DIOCGDISKINFO method. Both methods return the same

Re: disk driver interface

On Dec 29, 3:00am, Michael van Elst wrote: } } Currently NetBSD has three programming interfaces to determine } disk geometry from userland. } } - ioctl DIOCGDINFO. The traditional interface, limited to 32bit } numbers or disks 2TB because its data structure corresponds } to the binary

Re: disk driver interface

On Dec 29, 4:46pm, Christos Zoulas wrote: } In article m7qg4d$3kt$1...@serpens.de, } Michael van Elst mlel...@serpens.de wrote: } } Currently NetBSD has three programming interfaces to determine } disk geometry from userland. } } - ioctl DIOCGDINFO. The traditional interface, limited to 32bit }

Re: disk driver interface

On Dec 30, 6:42am, David Holland wrote: } On Tue, Dec 30, 2014 at 02:50:14AM +, Christos Zoulas wrote: } In article 20141229233211.ga10...@netbsd.org, } David Holland dholland-t...@netbsd.org wrote: } } It might be a good idea to do this for our own use, but probably it }

Re: kernel constructor

On Nov 12, 1:46am, Masao Uebayashi wrote: } On Wed, Nov 12, 2014 at 1:15 AM, Kamil Rytarowski n...@gmx.com wrote: } From David Holland } Please don't do that. Nothing good can come of it - you are asking for } a thousand weird problems where undisclosed ordering dependencies } silently

Re: MI linker script

On Nov 9, 11:52am, Masao Uebayashi wrote: } On Sun, Nov 9, 2014 at 11:22 AM, John Nemeth jnem...@cue.bc.ca wrote: } The question wasn't simply about ld -r stuff. It was about } the entire program of config(1) changes, linking changes, module(9) } changes, etc. There's an awful lot

Re: MI linker script

On Nov 9, 1:25am, Masao Uebayashi wrote: } On Sat, Nov 8, 2014 at 11:53 PM, Christos Zoulas chris...@astron.com wrote: } depending on ld -r to work properly } } I know none of you trust me, but you don't trust ld -r? It has nothing to do with trust. It's more like wanting to know what

Re: MI linker script

On Nov 9, 10:35am, Masao Uebayashi wrote: } On Sun, Nov 9, 2014 at 5:07 AM, John Nemeth jnem...@cue.bc.ca wrote: } On Nov 9, 1:25am, Masao Uebayashi wrote: } } On Sat, Nov 8, 2014 at 11:53 PM, Christos Zoulas chris...@astron.com wrote: } } depending on ld -r to work properly } } } } I know

Re: asymmetric smp

On Apr 2, 1:55pm, Johnny Billquist wrote: } On 2014-04-01 23:04, Warner Losh wrote: } 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

Re: Closing a serial device takes one second

On Feb 6, 1:22pm, Dennis Ferguson wrote: } On 6 Feb, 2014, at 12:18 , Marc Balmer m...@msys.ch wrote: } Actually the one second delay is wrong. If you want to de-assert DTR } for a modem to hangup, then do it in the application. } } You've clearly not run a bank of dial-in/out modems on a

Re: The lamentation of proplib(3)

On Jan 28, 7:40pm, Christian Koch wrote: } On Tue, Jan 28, 2014 at 06:44:57PM +, Mindaugas Rasiukevicius wrote: } and my own dissatisfaction has reached the point where I decided to raise } the question. The question of replacing proplib(3) with a better library. } There were ideas by

Re: in which we present an ugly hack to make sys/queue.h CIRCLEQ work

On Nov 24, 5:25am, Mouse wrote: } } Well, mrg wrote, when starting the thread, } } while preparing to update to GCC 4.8 i discovered that our } sys/queue.h CIRCLEQ macros violate C aliasing rules, ultimately } leading to the compiler eliding comparisons it declared as always } false. } }

Re: in which we present an ugly hack to make sys/queue.h CIRCLEQ work

On Nov 23, 2:16pm, Dennis Ferguson wrote: } On 22 Nov, 2013, at 21:40 , David Holland dholland-t...@netbsd.org wrote: } So ... looking at this code ... it seems like the core problem is that } TAILQ_HEAD and TAILQ_ENTRY are two different types (even though they } literally the same structure

Re: A Library for Converting Data to and from C Structs for Lua

On Nov 17, 11:02pm, Marc Balmer wrote: } Am 17.11.13 20:40, schrieb Lourival Vieira Neto: } On Sun, Nov 17, 2013 at 4:39 PM, David Holland dholland-t...@netbsd.org wrote: } On Sun, Nov 17, 2013 at 01:32:03PM +0100, Hubert Feyrer wrote: }I plan to import it and to make it available to both

Re: zero-length symlinks

On Nov 3, 2:57pm, Sverre Froyen wrote: } On 2013-11-03, at 11:47, Hubert Feyrer hub...@feyrer.de wrote: } On Sat, 2 Nov 2013, David Holland wrote: } I think not sensible is not a good enough reason to prohibit } something. } } Yeah yeah, but still nowadays we don't allow adding hard links

module path message

I've made a patch to the module subsystem to print the default module load path during initialisation. The reason for doing this is that certain arch/machine combos don't work with the standard modules for their archs and require custom built modules. This is the case for several evbppc

Re: module path message

On Oct 30, 11:00am, Alan Barrett wrote: } On Tue, 29 Oct 2013, John Nemeth wrote: } The default path for module loading is: /stand/amd64-xen/6.99.25/modules } } I suggest exposing the path via sysctl, and printing the sysctl } mib name in the message, something like } } kern.module.path

Re: module path message

On Oct 30, 12:40pm, Marc Balmer wrote: } Am 30.10.13 10:00, schrieb Alan Barrett: } On Tue, 29 Oct 2013, John Nemeth wrote: } The default path for module loading is: /stand/amd64-xen/6.99.25/modules } } I suggest exposing the path via sysctl, and printing the sysctl mib name } in the message

Re: How to hot swap an SCA SCSI disk with NetBSD

On Oct 25, 2:20pm, Mouse wrote: } } Generally speaking, SCA SCSI drives are hot-swap capable. } } Sure...but the drive bays aren't necessarily. For example, the drive } bay in a SS20 probably isn't; you can't even get to it without removing } the lid, so there'd've been little reason for Sun

Re: Lua in-kernel (lbuf library)

On Oct 18, 11:03am, Marc Balmer wrote: } Am 18.10.13 10:43, schrieb Artem Falcon: } Marc Balmer marc at msys.ch writes: } Justin Cormack justin at specialbusservice.com writes: } I have been using the luajit ffi and luaffi, which let you directly } use C structs (with bitfields) in Lua to do

Re: Lua in-kernel (lbuf library)

On Oct 19, 12:13am, Artem Falcon wrote: } 18.10.2013, × 21:03, John Nemeth jnem...@cue.bc.ca wrote: } On Oct 18, 11:03am, Marc Balmer wrote: } } Am 18.10.13 10:43, schrieb Artem Falcon: } } Marc Balmer marc at msys.ch writes: } } Justin Cormack justin at specialbusservice.com writes: } } I

Re: POSIX Semaphores

On Jun 9, 7:19pm, Paul Goyette wrote: } } According to the man page sem(4), one needs to include options } P1003_1B_SEMAPHORE in the kernel config file in order to support this } feature. Yet, the file kern/uipc_sem.c is included unconditionally in } all kernels, and there appears to be

Re: MI boot args revamp?

On May 22, 9:38am, Jean-Yves Migeon wrote: } Le 29/12/12 22:23, Jeff Rizzo a écrit : } On 12/29/12 1:12 PM, Greg Troxel wrote: } I would like to have a way to pass a string composed of the same flags } (we can continue to use our existing -a, -s and other flags) in a } consistent

Re: lua(4), non-invasive and invasive parts

On May 21, 6:10am, Marc Balmer wrote: } } this is going to upset dyoung i'm sure :) but it seems to me that } if these invasive changes to individual subsystems are needed like } this, and we want them to be optional, then imo they should be on } a per-subsystem basis, not global. eg

  1   2   >