On 3 Mar 2023, at 03:14, Crystal Kolipe
wrote:On Thu, Mar 02, 2023 at 09:06:17AM -0700, Theo de Raadt wrote:
What next? /dev/multiply -- you write two 32-bit values and then
you can
read a new 32 bit value?
Actually, that sounds quite cool :-).
https://9front.org needs you
On Fri, Mar 03, 2023 at 10:31:58AM +0100, Janne Johansson wrote:
> Of course it is ridiculous when you can just make a small mfs and fill it up.
As a non-root user?
Den fre 3 mars 2023 kl 10:15 skrev Crystal Kolipe :
> The intended use of full is for testing how simple shell scripts behave when
> they hit an unwritable file.
>
> > It should simply skip doing the round-trip through kernel.
>
> This comment is pure bullshit. Applicable to the python case and ba
On Thu, Mar 02, 2023 at 07:18:41PM -0700, Theo de Raadt wrote:
> What is with the long mail?
Theo:
Daniel Dickman asked a question to me, on-list. I provided the answer,
and tried to close the issue once and for all to avoid further replies.
You replied to the thread.
List:
The truth is that
You clearly do. You're replying to it, and seem to have strong feelings
on the matter.
On Thu, Mar 02, 2023 at 07:18:41PM -0700, Theo de Raadt wrote:
> Does anyone give a shit, besides you?
What is with the long mail?
Does anyone give a shit, besides you?
No.
Noone has any space for this bullshit, or this long explanation.
Crystal Kolipe wrote:
> On Thu, Mar 02, 2023 at 04:57:10PM -0500, Daniel Dickman wrote:
> > I don???t see the point of implementing /dev/full. The python regr
On Thu, Mar 02, 2023 at 04:57:10PM -0500, Daniel Dickman wrote:
> I don???t see the point of implementing /dev/full. The python regress test
> is the only time I???ve personally run into this. And I think the issue was
> that python???s test suite made wrong assumptions about what devices exist
> o
I don’t see the point of implementing /dev/full. The python regress test is the
only time I’ve personally run into this. And I think the issue was that
python’s test suite made wrong assumptions about what devices exist on a
particular system. Therefore the fix needed to be on the python side.
Hi Theo,
On Thu, Mar 02, 2023 at 09:06:17AM -0700, Theo de Raadt wrote:
> While at it, maybe we need a /dev/bullshit linked to /dev/random??
>
> This extra node looks like bullshit to me.
>
> It is encouraging a large application to do a round-trip through the
> kernel, for a rare occurance.
Th
On 2023/03/02 10:50, Dave Voutila wrote:
> Is this really a problem with ports? That Python issue was related to a
> Python 2.7 unit test and from 2014.
not really, no. there has been the odd patch over the years but nothing
current (no more than 4 including the Python one).
While at it, maybe we need a /dev/bullshit linked to /dev/random??
This extra node looks like bullshit to me.
It is encouraging a large application to do a round-trip through the
kernel, for a rare occurance.
It should simply skip doing the round-trip through kernel.
What next? /dev/multiply --
On Thu, Mar 02, 2023 at 10:50:08AM -0500, Dave Voutila wrote:
>
> Crystal Kolipe writes:
>
> > We currently don't implement the /dev/full device, which is present in
> > NetBSD, FreeBSD, and Linux.
> >
> > For those who haven't heard of it, it's basically the same as /dev/zero, but
> > writes to
Crystal Kolipe writes:
> We currently don't implement the /dev/full device, which is present in
> NetBSD, FreeBSD, and Linux.
>
> For those who haven't heard of it, it's basically the same as /dev/zero, but
> writes to it always return ENOSPC.
>
> The lack of /dev/full on OpenBSD has previously
13 matches
Mail list logo
