On Sun, Feb 25, 2024 at 04:16:03AM -, Michael van Elst wrote:
> t...@panix.com (Thor Lancelot Simon) writes:
>
> >Probably not a good idea to start with lseek() because if you _do_
> >encounter a tape device, seeking to SEEK_END could take you an extremely
> >long ti
s is not always the right design
choice.
As simple as possible, but no simpler.
--
Thor Lancelot Simont...@panix.com
"The inconsistency is startling, though admittedly, if consistency is to
be abandoned or transcended, there is no problem." - Noam Chomsky
On Thu, Feb 22, 2024 at 12:08:14PM +, Sad Clouds wrote:
> Hello, thanks to everyone who responded with their suggestions. Using
> various non-portable ioctls I can device size on most platforms, for
> both block and raw devices.
>
> This is more convoluted than a single lseek() call, but it is
On Wed, Feb 21, 2024 at 09:20:55PM +, Taylor R Campbell wrote:
> > Date: Wed, 21 Feb 2024 10:52:55 +
> > From: Sad Clouds
> >
> > Hello, for most operating systems determining the size of a block
> > device can be done with:
> >
> > lseek(fd, 0, SEEK_END);
> >
> > However, on NetBSD thi
On Thu, Feb 22, 2024 at 05:47:55AM +, Sad Clouds wrote:
> On Wed, 21 Feb 2024 12:48:34 -0800
> Jason Thorpe wrote:
>
> >
> > > On Feb 21, 2024, at 2:52???AM, Sad Clouds
> > > wrote:
> > >
> > > Hello, for most operating systems determining the size of a block
> > > device can be done with
R=/, postinstall(8) runs `certctl rehash' to make
> sure /etc/openssl/certs is populated.
>
> Note: This is limited to DESTDIR=/, and will not happen in
> cross-built destdirs, because it requires running openssl(1), and we
> don't have openssl(1) hooked up to the tools build, nor do we
> currently require the build environment to support it.
>
> If we changed either of those we could lift the restriction of
> DESTDIR=/ for postinstall(8) to run `certctl rehash'. (An
> alternative would be to test whether `type openssl' succeeds, but
> that strikes me as a little sketchier.)
--
Thor Lancelot Simont...@panix.com
"The inconsistency is startling, though admittedly, if consistency is to
be abandoned or transcended, there is no problem." - Noam Chomsky
gt; of reasons, not the least of which is that we removed critical parts
> > > of gcc2 support from /usr/include years ago so it's not been exercised
> > > in at least that long.
> >
> > ITYM gcc1? Note "less than&
On Mon, Feb 15, 2021 at 12:15:28PM -0500, Mouse wrote:
> > Does NetBSD provide any framework that allows USB device
> > ownership/permissions to be autmatically set on USB
> > VendorId/DeviceId?
>
> As far as I know it doesn't; a quick look at 8.0's manpages didn't show
> me anything. (9.1 is not
On Fri, Jan 15, 2021 at 12:21:24AM +, Taylor R Campbell wrote:
>
> What about them? Systems without usable microphone noise are no worse
> off than they would have been without nia's suggestion.
There are actually a couple of things that can be done here.
1) It's likely better to max out th
On Sat, Nov 21, 2020 at 07:50:02AM +, David Holland wrote:
> On Sun, Nov 15, 2020 at 03:10:08AM +0100, Kamil Rytarowski wrote:
> > I'm going to summarize the situation with formatters in the NetBSD base.
>
> A couple more points:
>
> > [...] old groff in base.
>
> There's an additional rea
On Sun, Oct 25, 2020 at 03:45:56PM -0400, Mouse wrote:
>
> I once had an hp300 with all of 5M of RAM. Years ago, when I had it
> running, thorpej told me it was quite possibly an instance of the
> slowest machine then supported by NetBSD. (Amusingly, at the same time
> I had an alpha that he sai
On Sun, Oct 25, 2020 at 02:13:47AM +0200, Kamil Rytarowski wrote:
>
> I recall catpages to used in 80286 UNIX (Coherent) and the catpages are
> probably just applicable for such constrained environments that cannot
> host any text formatters.
The issue was the speed of the text formatters. I viv
On Tue, May 12, 2020 at 10:00:20AM +0300, Andreas Gustafsson wrote:
>
> Adding more sources could mean
> reintroducing some timing based sources after careful analysis, but
> also things like having the installer install an initial random seed
> on the target machine (and if the installer itself la
On Mon, May 11, 2020 at 04:16:12PM -, Michael van Elst wrote:
> n...@netbsd.org (nia) writes:
>
> >is insisting). All of that depends on assumptions and trust - it
> >does no measurement of the value of the entropy being provided.
>
> Previously we could trust in random processes, whether the
On Mon, May 11, 2020 at 04:28:51PM +0300, Andreas Gustafsson wrote:
>
> For the OpenBSD strategy to work, the system needs to actually refuse
> to run if the seed can't be loaded (or full entropy achieved in some
> other way). NetBSD doesn't do that. As long as there is any way
Well, no. The s
On Mon, May 11, 2020 at 09:53:31AM +0300, Andreas Gustafsson wrote:
>
> OpenBSD guarantees that there is an entropy seed from the boot loader,
> which is very different from NetBSD's "best effort". Was this not
> already the case when the getentropy API was introduced?
I think you need quotes ar
livered
"high quality entropy" is, as far as I'm concerned, roughly like the
notion that a ball flying upwards out of my hand is evidence that
gravity reversed directions.
--
Thor Lancelot Simon t...@panix.com
"Whether or not there&#x
On Sat, May 09, 2020 at 05:30:18PM +0200, Joerg Sonnenberger wrote:
> On Sat, May 09, 2020 at 03:25:25PM +, nia wrote:
> > On Sat, May 09, 2020 at 01:13:44PM +, nia wrote:
> > > Right, yes, the CPUID stuff wasn't being defined when builing EVP which
> > > meant the dumb asm implementation w
On Fri, May 08, 2020 at 10:24:43PM +, m...@netbsd.org wrote:
>
> The indirection only applies to the first call. The magic is within
> rtld.
If it's not binary patch, no magic can avoid at least one level of
indirection.
--
Thor Lancelot Simon
On Fri, May 08, 2020 at 10:03:06AM +0200, Kamil Rytarowski wrote:
> On 08.05.2020 02:14, Thor Lancelot Simon wrote:
> >
> > Not without performance penalty for every atomic operation, unless you
> > propose
> > to do this by binary patch as is done in the kernel.
&
On Fri, May 08, 2020 at 01:51:16AM +0200, Kamil Rytarowski wrote:
> A runtime detection could be a part of ifunc (is it ready for NetBSD?).
>
> The standard C/C++ feature is to detect whether atomic operations are
> real (lock-free) through atomic_is_lock_free(). This is a feature, not a
> bug (as
On Sun, May 03, 2020 at 10:48:41AM +0200, Kurt Roeckx wrote:
>
> You might want to read https://lwn.net/Articles/808575/
To be blunt (I think it's past time for it): I trust Taylor reading the
code more than I trust you reading stuff you found with Google.
Thor
always has entropy to
provide.
--
Thor Lancelot Simon t...@panix.com
"Whether or not there's hope for change is not the question. If you
want to be a free person, you don't stand up for human rights because
it will work, but because it is right." --Andrei Sakharov
On Tue, Feb 04, 2020 at 08:36:56AM -0500, Thor Lancelot Simon wrote:
>
> Moving part of the system to /usr was a *necessary evil* when it was done.
> There is no real rhyme nor reason to what's in /bin vs /usr/bin, even less
> to /sbin vs /usr/sbin, except "huh, I need _th
On Tue, Feb 04, 2020 at 07:38:34AM +1030, Brett Lymn wrote:
>
> and mounted. So, so what if you get / first and then have to wait for
> the rest of the fsck's to happen vs a fsck of a single large file
> system? At the end of the day it will take about the same amount f time
> to get the machine
On Wed, Jan 29, 2020 at 11:33:22AM +0100, Joerg Sonnenberger wrote:
> On Tue, Jan 28, 2020 at 09:21:23PM +, Roy Marples wrote:
> > To fix this, I suggest that we split syslogd into syslogd and
> > syslogd-network.
>
> We could also do a much simpler and more radical decision and stop
> splitt
ares DHCP serving on OpenBSD at least.
>
> Is this to generic and we should have a _dhcpcd user or is _dhcp satisfactory?
I don't think it's a great idea to share the user between the purposes, even
though few systems will simultaneously be DHCP server a
On Fri, Aug 30, 2019 at 02:40:06PM +1000, matthew green wrote:
> hi folks.
>
>
> a very long time ago in netbsd years tls@ patched GCC to use
> /tmp over /var/tmp, for the compiler temporaries.
>
> i tried to keep these patches, but they got lost at some
> point and when i recently wanted to dea
On Wed, Aug 28, 2019 at 10:42:13PM -0400, Thor Lancelot Simon wrote:
> On Wed, Aug 28, 2019 at 01:54:54AM +0100, Roy Marples wrote:
> > > > >
> > > > > Where 8.2 is taken from the .so version?
> > > > >
> > > > > Roy
> > >
l.
The problem with using the solib version is that it may differ on
platforms derived from NetBSD even if the curses API is exactly the same.
This would, for example, have been the case on EQ/OS which I maintained
at Coyote Point - we bumped all the shlib versions at least once because
of a chan
On Fri, Aug 02, 2019 at 09:29:27PM -0700, Matt Turner wrote:
>
> So great, you made your API incompatible with everyone else for zero
> gain. /o\
And so forth.
Is there some reason for the snotty attitude? Whether you're right or
wrong you're not likely to persuade anyone that way.
Thor
On Tue, Jul 09, 2019 at 10:24:53AM -0700, Graham Percival wrote:
> On Tue, Jul 09, 2019 at 07:17:39AM +0200, Martin Husemann wrote:
> > The classical "data segment" (limited by RLIMIT_DATA) is not used much
> > nowadays in NetBSD. Especially malloc() does not use it.
> >
> > RLIMIT_DATA T
On Fri, Apr 26, 2019 at 11:36:00PM +0200, Kamil Rytarowski wrote:
>
> I propose a patch that:
>
> 1. Removes alternative versions of depending on preprocessor
> namespace definitions. All code since now is assumed to be
> reentrant/threading safe.
Benchmark results? Pessimizing the single-thre
On Fri, Apr 12, 2019 at 03:46:15AM +0200, Emmanuel Dreyfus wrote:
> Thor Lancelot Simon wrote:
>
> > Gluster on Linux hitting 9Gb/sec for sequential I/O
>
> Well at that performance level, avoiding copies is certainly a must, but
> I cannot test that because I lack the h
On Fri, Apr 12, 2019 at 01:55:39AM +0200, Emmanuel Dreyfus wrote:
>
> On the performance front, it is true that the perfuse stack will cause
> data to be copied back and forth. When I started it, I thought that I
> would quickly have to add shared memory tricks to avoid copying data,
> but it has
On Sat, Mar 23, 2019 at 08:28:38AM +0100, Emmanuel Dreyfus wrote:
> Thor Lancelot Simon wrote:
>
> > Hold your nose and TIOCSTI.
>
> That let's me inject data as if it was typed on the terminal right? You
> suggest I steal input from console and reinject it using T
On Fri, Mar 22, 2019 at 04:11:31PM +, Emmanuel Dreyfus wrote:
> Hello
>
> I would like to execute a scipt when a function key is pressed on the
> console. Is there a mechanism to detect keypresses on wscons? If I
> make a daemon that opens /dev/console it will steal the input from
> getty/lo
On Thu, Mar 21, 2019 at 10:15:52AM +0100, Edgar Fu? wrote:
> > IIRC Irix had this, both for EFS and XFS.
> No, as far as I remember and see, neither dump nor xfsdump had this.
> I didn't actually start my O2, though.
I'm pretty sure it did -- dumpdates on Irix tracked the last-dumped
date for arbi
ed for soemthing else there!
IIRC Irix had this, both for EFS and XFS.
--
Thor Lancelot Simon t...@panix.com
"Whether or not there's hope for change is not the question. If you
want to be a free person, you don't stand up for human
On Fri, Feb 15, 2019 at 09:47:37PM +0100, Kamil Rytarowski wrote:
>
> Colors nowadays are industry standard and increase readability.
Your unqualified statement is objectively false.
How do you know that the user's terminal isn't using the same
color -- or all too close to it -- for background a
On Mon, Dec 31, 2018 at 06:35:20PM +0200, Artturi Alm wrote:
> Hi,
>
> i'd like to have the functionality given by the diff below, before
> cleaning up another diff making use of it.
LGTM - please make sure these are used as entropy sources, IIRC I
hardcoded the sensor types when I originally did
On Sat, Dec 15, 2018 at 10:08:00PM +, Taylor R Campbell wrote:
>
> Given that a large fraction of respondents (though not all) indicated
> that their primary use of telnet is to test reachability of a server
> or manually enter SMTP or HTTP requests over the internet -- a use
> which is adequa
On Sun, Aug 05, 2018 at 12:22:04AM +0200, Joerg Sonnenberger wrote:
> On Thu, Aug 02, 2018 at 09:26:00PM -0400, Thor Lancelot Simon wrote:
> > On Thu, Aug 02, 2018 at 01:46:35PM +0200, Joerg Sonnenberger wrote:
> > > On Wed, Aug 01, 2018 at 11:54:10PM -0400, Thor Lancelot Simon
On Thu, Aug 02, 2018 at 01:46:35PM +0200, Joerg Sonnenberger wrote:
> On Wed, Aug 01, 2018 at 11:54:10PM -0400, Thor Lancelot Simon wrote:
> > On Tue, Jul 31, 2018 at 08:28:19AM +, Christos Zoulas wrote:
> > > In article <2c408f23-6eae-da00-dfb2-ebc7b66e6...@gmx.com>
27;d also be "cut arm", I think, since the kernel profiling that
relies on the same tools does still work, and, though limited, can do
some things out of the box that take nontrivial effort with the DTrace
FBT provider, the nearest alternative.
--
Thor Lancelot Simon
On Thu, Jun 21, 2018 at 04:12:32PM +0100, Roy Marples wrote:
>
> The release of NetBSD-8 is probably imminent, now is probably the best time
> to do this.
I would favor removing dhclient from base for NetBSD-8, even at this late
date.
Thor
On Tue, Nov 14, 2017 at 05:35:54PM -0500, Izaac wrote:
> On Sat, Nov 11, 2017 at 08:10:57PM +0700, Robert Elz wrote:
> > It is unreasonable to inflict on people who don't want/need it, just
> > because it happens to be useful to you.
>
> Elz? Robert Elz? The same one I chastised for a bunch of u
l$20bsd%7Csort:relevance/muc.lists.freebsd.hackers/JaNrZz8_3LU/pI5cvX552WgJ
also discusses this, down towards the bottom of the thread.
Anyway, it seems highly likely this program came from BSD
Unix or perhaps its cousin Research Unix. Welcome back.
--
Thor Lancelot Simon
On Mon, Oct 02, 2017 at 02:48:12AM +0700, Robert Elz wrote:
>
> With this, just commit it (don't forget the set lists).
What he said.
Thor
On Sun, Oct 01, 2017 at 03:24:06PM +, Valery Ushakov wrote:
>
> It doesn't work the same for multiple files.
I guess the question is whether we ought to have this if it can be made to
work the same way for multiple files.
My inclination is "yes". It's low risk (unlike, say, modifying
the pa
On Thu, Jul 13, 2017 at 09:01:26AM -0400, Izaac wrote:
> On Thu, Jul 13, 2017 at 07:46:39AM +0700, Robert Elz wrote:
> > So, opinions?
>
> Stop.
>
> Leave /bin/sh alone.
I strongly disagree and note the obvious internal inconsistency in your
argument (such as it is):
> If you want features for
On Wed, Jul 12, 2017 at 04:12:55PM +0200, Edgar Fu? wrote:
> I know about daemon(3). I'm aware this question is not NetBSD-specific.
> However, I want to be able to write portable code. Plus there's so much
> nonsense around on the subject that I want to make sure I'm understanding
> things corr
Captive-portal login is a very real problem. How best to solve it otherwise?
Remember, small embedded systems (easily supported by adding additional sets
using our existing framework) are within scope.
--
Thor Lancelot Simont...@panix.com
"We ca
ake 8 hours on a
> weak laptop).
You don't need to do a full release build to check that you got the
setlists right. You just need to do the "sets" step. This was part
of my standard development workflow (on an anemic laptop, often on
the train with little connectivity) for 6 years
On Sat, Jun 24, 2017 at 11:27:47AM +0200, Martin Husemann wrote:
> On Fri, Jun 23, 2017 at 10:27:40PM +0200, Kamil Rytarowski wrote:
> > 3. Disable float128 in libstdc++ for everybody.
>
> You are missing the obvious one:
>
> 4. Disable float128 for all architectures that have no hardware suppo
ng from /dev/urandom cannot block, and never could unless the
system on which you observed such behavior had a bug.
--
Thor Lancelot Simont...@panix.com
"We cannot usually in social life pursue a single value or a single moral
aim, untroubl
On Sun, Jun 04, 2017 at 08:16:16PM +0200, Emmanuel Dreyfus wrote:
> Thor Lancelot Simon wrote:
>
> > One key idea that may help you is not mine -- it's due to Matt Thomas. It
> > is
> > the idea of, making an *additional* bunch of sets files specifying
> >
On Mon, May 15, 2017 at 02:37:17PM +0300, Jukka Marin wrote:
>
> I'm wondering what would be the best way of system updates. I would
> like to have two separate system images, one that is active and running
> and another which can be updated. At boot time, the system would have
> to check which
t (which is I guess what ksh/bash do)?
What happens if I pull in a shell function library with "."? Do I get line
numbers per-file, or does the inclusion cause line numbers to appear to jump
_within_ the file that included, or...?
--
Thor Lancelot Simon
tion starts at a nonzero offset, which is the typical layout
> on i386 and amd64.
Easy to work around this with dd -- it's basically what it was originally
designed for!
Admittedly the temporary files generated by this workflow may be rather
large.
--
Thor Lancelot Simon
On Fri, Sep 02, 2016 at 10:26:51AM -0400, Thor Lancelot Simon wrote:
> On Fri, Sep 02, 2016 at 03:25:52AM +0200, William Z. wrote:
> > Hi,
> >
> > I'm currently trying to replace Linux with NetBSD in some of
> > my embedded devices.
> >
> > I have re
On Fri, Sep 02, 2016 at 03:25:52AM +0200, William Z. wrote:
> Hi,
>
> I'm currently trying to replace Linux with NetBSD in some of
> my embedded devices.
>
> I have read "The Guide" and found out how to create a crosscompiler and
> compile a tiny custom kernel. However, I also want to create a ve
On Sat, Aug 13, 2016 at 10:06:35PM +0200, Jarom??r Dole??ek wrote:
> FWIW, build of tools for both i386 and sparc64 finished without
> problems for me on Mac OS X host (10.11.6), building from clean
> sources.
The problem is not with the tools build.
Thor
For the past several days, building on OS X 10.9.5 has failed with what
looks like a symptom of host/target confusion that could have more serious
consequences (like bad builds on other platforms). This is new. Hubert
has also seen it on OS X 10.5.
Build command is "build.sh -m amd64 -U -u distr
On Thu, Aug 11, 2016 at 04:05:06PM +0100, Robert Swindells wrote:
>
> >2) /usr/bin/cc:
> >Undefined symbols for architecture x86_64: "_iconv"
> >in external/gpl3/gcc/usr.bin/backend
>
> This should be in libc.
For what value of "should"? _iconv is in the implementation-defined
namespace
s) is achieved whether the "no" deletes
> it or whether it never existed in the first place.
I like this better.
--
Thor Lancelot Simont...@panix.com
"The dirtiest word in art is the C-word. I can't even say 'craft'
without feeling dirty."-Chuck Close
On Fri, Jun 24, 2016 at 01:34:52PM +, co...@sdf.org wrote:
> Hi,
>
> There's a lot of programs sticking around since a long time, and are
> less useful today. at the very least, they do not need to be in
> base.tgz, which means they take up space even in minimal installs.
>
> Examples:
> eker
On Wed, May 11, 2016 at 10:37:58PM -0700, Charles Cui wrote:
> Hi Christos,
>
>I got the new list post below. Note that the second list is build with
> -D_NETBSD_SOURCE -lpthread -lrt -lm
If you have a proper NetBSD build environment (native or cross compilation)
then -D_NETBSD_SOURCE seems w
On Mon, May 09, 2016 at 10:58:50AM +0930, Brett Lymn wrote:
> On Mon, May 09, 2016 at 12:53:02AM +, Christos Zoulas wrote:
> >
> > Heh that's funny. He should then run the build.sh command with the old
> > tooldir name or make a symlink from the old tooldir name to the new one.
> >
>
> Why n
> > | sigpause
> > | sigrelse
> > | sigset
> > |
> > | mmap:
> > | POSIX_TYPED_MEM_ALLOCATE
> > | POSIX_TYPED_MEM_ALLOCATE_CONTIG
> > | POSIX_TYPED_MEM_MAP_ALLOCATABLE
> > | struct posix_typed_mem_info
> > | posix_mem_offset
> > | posix_typed_mem_get_info
> > | posix_typed_mem_open
> >
> > I dont know what these are
> >
> > | aio
> > | struct rlimit
> >
> > We have struct rlimit, again we need to check the compilation flags.
> >
> > | cpuset
> > | CPU_ZERO
> > | CPU_SETSIZE
> > | CPU_SET
> > | cpu_set_t
> >
> > This is linux-specific; we have our own and the tests need to be adjusted
> >
> > |
> > | semaphore
> > | _SC_SEM_NSEMS_MAX
> > | features.h
> >
> > christos
> >
--
Thor Lancelot Simont...@panix.com
"We cannot usually in social life pursue a single value or a single moral
aim, untroubled by the need to compromise with others." - H.L.A. Hart
On Thu, Mar 24, 2016 at 11:55:25AM +, Roy Marples wrote:
> Lets go back to the original question.
>
> On 20/03/2016 09:26, Michael van Elst wrote:
> > r...@marples.name (Roy Marples) writes:
> >
> >> So I've created pidfile_lock (patch attached) to address these problems.
> >
> > Does it wor
On Mon, Mar 21, 2016 at 04:44:40PM +, Roy Marples wrote:
>
> foo starts as PID 10, links /var/foo and writes 10 to it.
"As simple as possible but no simpler". Don't just write 10, write
hostname-proctitle-10 (this is an old solution too; trn does it).
Thor
On Mon, Mar 21, 2016 at 02:30:43PM +, Roy Marples wrote:
> >
> > In fact, what you really want is just the guts of shlock(1), specifically
> > the shlock -p behavior. I can't see any reason why pidfile shouldn't just
> > do exactly what shlock -p does, except with a C rather than a shell
> >
On Sun, Mar 20, 2016 at 08:43:31PM -0400, Thor Lancelot Simon wrote:
> On Sun, Mar 20, 2016 at 08:53:03PM +, Roy Marples wrote:
> > On Sunday 20 March 2016 14:53:46 you wrote:
> > > On Sat, 19 Mar 2016 23:29:37 +
> > >
> > > Roy Marples wrote:
> &g
On Sun, Mar 20, 2016 at 08:53:03PM +, Roy Marples wrote:
> On Sunday 20 March 2016 14:53:46 you wrote:
> > On Sat, 19 Mar 2016 23:29:37 +
> >
> > Roy Marples wrote:
> > > pidfile(3) is pretty crap - it just writes to the file without any
> > > locking.
> >
> > I don't understand why you
75 matches
Mail list logo
