Adam Thompson wrote:
> On 2019-08-03 18:14, Theo de Raadt wrote:
> > Adam Thompson wrote:
> >
> >> Summary: I open cua0 with cu(1), quit cu(1), try to re-open with
> >> cu(1) but now it immediately fails with EBUSY. *Usually* doesn't
> >> happen with USB-to-serial (cuaU[0-9]) but have still
On 2019-08-03 18:14, Theo de Raadt wrote:
Adam Thompson wrote:
Summary: I open cua0 with cu(1), quit cu(1), try to re-open with
cu(1) but now it immediately fails with EBUSY. *Usually* doesn't
happen with USB-to-serial (cuaU[0-9]) but have still seen it once or
twice.
[...]
You are
Ha. I was about to start out with how I can guess how complicated managing
an operating system is. Then I see the last line of your email saying, "How
about if you don't know, stop making guesses".
My comments only apply to my experience coding for bluetooth on mobile
devices and it was just
Bryan Wright wrote:
> > On Aug 7, 2019, at 10:06, Theo de Raadt wrote:
> >
> > Bryan Wright wrote:
> >
> >> Are there technical/philosophical problems that make all versions of
> >> Bluetooth incompatible with the project, or is it a just matter of
> >> removing what is not being maintained?
Wow, look -- more useless chatter on the topic.
The bt stack we had was designed as "network code", and all sorts of
complex layer violations and device hand-offs were very complicated and
troublesome.
The code was not deleted because bluetooth is shit. The code was
deleted *because it was
> On Aug 7, 2019, at 10:06, Theo de Raadt wrote:
>
> Bryan Wright wrote:
>
>> Are there technical/philosophical problems that make all versions of
>> Bluetooth incompatible with the project, or is it a just matter of
>> removing what is not being maintained?
>
> I'm sure a bunch of you can
Right, without reading the code and only reading this commit message
it's all conjecture.
I was just hoping to hear something more if someone was inclined to share.
inclined. The commit message seems like some sort of inside joke.
Log message:
"It's not the years, honey; it's the mileage."
Bryan Wright wrote:
> Are there technical/philosophical problems that make all versions of
> Bluetooth incompatible with the project, or is it a just matter of
> removing what is not being maintained?
I'm sure a bunch of you can come up with theories about what actually
transpired, without
Are there technical/philosophical problems that make all versions of Bluetooth
incompatible with the project, or is it a just matter of removing what is not
being maintained?
ok, thanks. Bluetooth is overcomplicated and if it's not managed properly
it just opens up the attack surface for no reason.
It definitely makes some things easy but there are always workarounds.
On Tue, Aug 6, 2019 at 11:52 PM Consus wrote:
> On 17:12 Tue 06 Aug, John Brahy wrote:
> > Hello,
Hi Claudio,
I did actually try putting my python plugin and unboundmodule.py into the
chroot, but I completely forgot that I would also need to install the rest of
python into the chroot! Haha
Serves me right for working on it until 1am when I should should have been
asleep and trying with
On Tue, Aug 06, 2019 at 11:17:04PM +0200, Sebastian Benoit wrote:
> Caleb(enlightened.des...@gmail.com) on 2019.08.06 08:05:48 -0700:
> > How do I publish default router preferences as defined in RFC 4191
> > (https://tools.ietf.org/html/rfc4191) using rad in OpenBSD 6.5?
> > I've read the
On Wed, Aug 07, 2019 at 08:44:07AM +0100, Andy Lemin wrote:
> Morning Stuart,
>
> So I’ve tested with the base build options properly, the initial errors I saw
> before have gone which is good. But I have a more fundamental issue with
> Unbound now sadly.
>
> Swig successfully built
Morning Stuart,
So I’ve tested with the base build options properly, the initial errors I saw
before have gone which is good. But I have a more fundamental issue with
Unbound now sadly.
Swig successfully built “/usr/src/unbound/pythonmod/unboundmodule.py” and
installed it to
On 17:12 Tue 06 Aug, John Brahy wrote:
> Hello,
>
> Just curious if there was any change in OpenBSD supporting bluetooth.
Sadly, there is none.
15 matches
Mail list logo
