On Tue, Mar 26, 2013 at 10:50:40PM +0400, Franco Fichtner wrote:
Nobody in their right mind would have such a system as
mission critical infrastructure. :)
What, like using a Honeywell 316 as a nuclear power station
reactor temperature monitor in to the early 2000s, until it's
hard disk failed?
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
On Mar 26, 2013, at 6:26 PM, Creamy cre...@nocrater.com wrote:
but I honestly question the utility of any of these ISA
network and SCSI drivers.
Perhaps somebody who is new to coding might be able to learn something
On 2013/03/26 18:06, Creamy wrote:
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
On Mar 26, 2013, at 6:26 PM, Creamy cre...@nocrater.com wrote:
Looking to the future, when are we going to drop 486 support, anyway?
Now, that's a more interesting thing ask.
How much
Hi,
I'm trying to install OpenBSD on my laptop with AR5424 but it fails. The
question is: wasn't the patch which I found (
http://marc.info/?t=12643791922) merged into OpenBSD official
repository or it's bugged?
Have maybe anyone tried testing/developing those patches since 2010?
Retards,
On 03/27/13 12:27, Hubert Jarosz wrote:
Hi,
I'm trying to install OpenBSD on my laptop with AR5424 but it fails. The
question is: wasn't the patch which I found (
http://marc.info/?t=12643791922) merged into OpenBSD official
repository or it's bugged?
If I remember well it breaks at
On Wed, Mar 27, 2013 at 10:43:53AM +, Stuart Henderson wrote:
On 2013/03/26 18:06, Creamy wrote:
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
On Mar 26, 2013, at 6:26 PM, Creamy cre...@nocrater.com wrote:
Looking to the future, when are we going to drop 486
Hi,
I have ported NetBSD's tmpfs to OpenBSD. The port should be functional
on i386 and amd64. I haven't tested on other architectures. There are
limitations: update of mount options is not supported and the number of
nodes in a tmpfs file system is limited by the number of anonymous UVM
objects
Hi,
The call to in_pcballoc() in user request attach is handled in three
different ways. Use the same code in udp_usrreq() and rip_usrreq()
and rip6_usrreq(). Also put an splsoftassert() into in_pcballoc()
for safety.
If I understand the code correctly, this also fixes a pcb and socket
leak in
Hi tech@.
Can OpenBSD use SSE4.2 CRC32 (found on Core i7) to speedup
TCP/IP checksum calculations?
Cheers,
Alexey
Hi,
Please, don't do this.
What exactly? You quoted my entire mail, but didn't narrow down exactly
which of my suggestions would cause problems for you.
I've jumped from OpenBSD to NetBSD boat when SCSI driver were rewritten
to the new version (between 3.1-stable and 3.2-stable), and my
On Tue, 26 Mar 2013 07:28:20 +0100, Ted Unangst wrote:
As much as it pains me to submit a diff that contains + in the compat
directory, this is still mostly -. Calling our mixer devices NetBSD
devices doesn't make a whole lot of sense. Also kill some other dead
code.
The below diff reflects
In fact, to everybody else who is reading this, doesn't it just point out
that 486 support is, effectively, already broken, (as I suspected),
because the devices that typically go with machines of that era are
suffering bit-rot in the tree?
Absolutely not. First, 80486 support is not broken
On Wed, Mar 27, 2013 at 10:04 PM, Miod Vallat m...@online.fr wrote:
Not sure about ancient 3Com's, but they are Ethernet at
least, in contract to Token-Ring device like tr*.
Do we support Token-Ring?
We used to, on TRopic boards, but since public documentation for TR
hardware amounts to
Do we support Token-Ring?
We used to, on TRopic boards, but since public documentation for TR
hardware amounts to zilch, and there is no interest in changing this
situation, it was eventually removed from the tree to clear the way of
other changes.
And with no TR stack, is there any
On Wed, Mar 27, 2013 at 08:05:47PM +, Miod Vallat wrote:
In fact, to everybody else who is reading this, doesn't it just point out
that 486 support is, effectively, already broken, (as I suspected),
because the devices that typically go with machines of that era are
suffering
On Wed, Mar 27, 2013 at 08:05:47PM +, Miod Vallat wrote:
In fact, to everybody else who is reading this, doesn't it just point out
that 486 support is, effectively, already broken, (as I suspected),
because the devices that typically go with machines of that era are
suffering bit-rot
Soekris NET4501 are still in use, and they are based upon 80486 cores.
`Key' ISA devices such as wdc are still heavily tested as pcmcia or such
attachments on i386 and non-i386 platforms. Other devices such as
com(4), pckbc(4), still exist on many systems, even if they are no
longer on
On 03/27/2013 01:01 PM, Creamy wrote:
Or, more realistically, perhaps you could just choose to maintain the
-patch branch of a particular version that was of interest to you. For
example, if we stopped supporting 486 in 6.0, by way of example, what
is to stop you taking 6.0 and maintaining a
On Wed, Mar 27, 2013 at 08:14:20PM +, Creamy wrote:
On Wed, Mar 27, 2013 at 08:05:47PM +, Miod Vallat wrote:
In fact, to everybody else who is reading this, doesn't it just point out
that 486 support is, effectively, already broken, (as I suspected),
because the devices that
What you're suggesting is a small part of the ISA code in the tree.
I did not want to list all isa drivers which happen to be tested a few
times every year either.
...and note that I've been working on the pckbc code for the last
couple of weeks, so I should be fully aware of it's existance.
On Wed, Mar 27, 2013 at 10:24 PM, Miod Vallat m...@online.fr wrote:
Do we support Token-Ring?
We used to, on TRopic boards, but since public documentation for TR
hardware amounts to zilch, and there is no interest in changing this
situation, it was eventually removed from the tree to
Creamy [cre...@nocrater.com] wrote:
Miod, you seem like an all-right bloke, and I don't want to create
bad feelings, but you're insulting me on a public mailing list,
because I dare to bring up something you object to.
Other people have been rude to me in private mail, because my views
Don't forget, though, this *is* open source. If the project officially
drops support for anything you like, ultimately you are free to fork it.
It is. And we are the developers, and you are not. So put a sock in it.
Really, this community has an attitude problem - and you *need*
more developers, believe me, you shouldn't be trying to scare
them away.
You're right. We need more developers.
What we don't need is more people who have the time to send 25
long opinionated rants to our mailing lists.
So put
On Wed, 27 Mar 2013 19:24:49 +
Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
However, I would be glad if the 486 support was kept as I have many
486 systems that I would like to be able to use if I ever get around
to porting the ethernet driver (which is open source).
Oops, just checked and
Alexey Suslikov alexey.susli...@gmail.com wrote:
Can OpenBSD use SSE4.2 CRC32 (found on Core i7) to speedup
TCP/IP checksum calculations?
TCP, UDP, and IPv4 checksums are simple sums and don't involve CRCs.
Also, the SSE4.2 CRC32 instruction uses the Castagnoli polynomial,
which is different
Hi
On i386:
$ ksh -c 'echo $((-2147483648 / -1))'
Floating point exception (core dumped)
$ ksh -c 'echo $((-2147483648 % -1))'
Floating point exception (core dumped)
Was the same at least on amd64 with LONG_MIN last I could check.
Perhaps something like this?
Index: expr.c
On Wed, Mar 27, 2013 at 3:56 PM, Nicholas Marriott
nicholas.marri...@gmail.com wrote:
case O_DIV:
case O_DIVASN:
+ if (vl-val.i == LONG_MIN vr-val.i == -1)
+ evalerr(es, ET_STR, can't represent result);
Sure, that actually looks to be what other shells do anyhow.
Index: expr.c
===
RCS file: /cvs/src/bin/ksh/expr.c,v
retrieving revision 1.21
diff -u -p -r1.21 expr.c
--- expr.c 1 Jun 2009 19:00:57 - 1.21
+++ expr.c
On Wed, Mar 27, 2013 at 4:15 PM, Nicholas Marriott
nicholas.marri...@gmail.com wrote:
Sure, that actually looks to be what other shells do anyhow.
That looks ok to me.
Which shells did you check, out of curiosity? On Goobuntu, both bash
and dash give SIGFPE too actually.
Checking POSIX, I
On Wed, Mar 27, 2013 at 04:27:22PM -0700, Matthew Dempsky wrote:
On Wed, Mar 27, 2013 at 4:15 PM, Nicholas Marriott
nicholas.marri...@gmail.com wrote:
Sure, that actually looks to be what other shells do anyhow.
That looks ok to me.
Which shells did you check, out of curiosity? On
And yet again for expr :-).
$ expr -2147483648 / -1
Floating point exception (core dumped)
expr on Linux (GNU or whatever it is) reports Numerical result out of
range for this. But it does the same for other overflows (such as expr
-9223372036854775808 - 1 on a 64-bit platform) where we just go
my thoughts inline...
On 03/26/13 05:20, Ted Unangst wrote:
These isa devs are already disabled and not particularly popular among
our users. affected: tcic, sea, wds, eg, el
Index: arch/i386/conf/GENERIC
===
RCS file:
Hi,
I'm re-posting this in hope. :)
http://marc.info/?l=openbsd-techm=135698142814632w=2
Please let me know if I can provide any further info.
- Michael
What does bpf have to do with the namecache? I was wondering the same
thing every time I saw bpf.o get recompiled after editing namei.h. Oh,
vnode.h includes namei.h. Just because.
Shuffle that line out to the exactly one place that needs it.
Index: kern/vfs_init.c
libkvm already figures out the pagesize of the machine in _kvm_open(),
and then allows the machine-dependent _kvm_initvtop() to override it
if need be (thereby, handling sparc). Thus we can avoid the PAGE_SIZE,
PAGE_SHIFT, ... variables.
Seems to be working ... wonder if I missed some relevant
I did not want to list all isa drivers which happen to be tested a few
times every year either.
OK, put it this way, there are at least some of the ISA drivers which
people are not using on a regular basis, and they are broken as a result
of that. Agree or not? We've *seen* examples of
37 matches
Mail list logo
