On Sat, Apr 27, 2019 at 04:55:50PM +0300, Gregory Edigarov wrote:
> attached please find dmesg and backtrace of X when that happen again
> hope this bug report will be more useful than previous one.
>
> thank you.
> --
> With best regards,
> Gregory Edigarov
Likely fixed by
On Fri, Apr 26, 2019 at 11:57:14AM -0700, Joe M wrote:
> Hello,
>
> I had this same issue with 6.4 and 6.5. Applying this patch has fixed
> the issue. I am using 2 radeon gpu's.
>
> https://patchwork.freedesktop.org/series/28284/
Thanks for the report and tracking this down. I've committed
On Sun, 28 Apr 2019 at 02:43, Thomas Frohwein wrote:
>
> On Sun, Apr 28, 2019 at 02:07:44AM +0700, Igor Podlesny wrote:
> [...]
> > Looks like decision made aren't subjects of discussing(?) Well, why
> > the hell you have those mail lists then(?) :)
>
> Igor:
> The actual purpose of misc@ is for
> I see that nothing has changed since the 70s, same moronic attitude towards
> people confused > by Unix shit.
I guess the attitude from people asking is the same like '70. Just
asking, I came in this world a few years late.
> the release has a bug / funny morons
A few dozen people taking
Anonymous writes:
> Some pointless bullshit or other
Turns out time's not as simple a concept as your average developer assumed.
Apparently you're going to have to learn some things. It could be a first!
Welcome to the real world.
Good luck.
Matthew
Theo de Raadt:
> cho...@jtan.com wrote:
>
>> Anonymous writes:
>>> Otto Moerbeek:
On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
> Here too: https://www.openbsd.org/65.html
Does it matter? It is very common for publications to be dated in the
future.
On 12:43 Sat 27 Apr, Thomas Frohwein wrote:
> Move along, nothing to see here.
I want to see more butthurting Theo!
cho...@jtan.com wrote:
> Anonymous writes:
> > Otto Moerbeek:
> > > On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
> > >
> > >> Here too: https://www.openbsd.org/65.html
> > >
> > > Does it matter? It is very common for publications to be dated in the
> > > future.
> > >
> > >
Otto Moerbeek writes:
>
> The mechanism is in the docs as well, not only in the code. You
You are of course correct, and OpenBSD has some of the best documentation
I've ever seen, but I've spent so long in linux land that whenever I'm
met with the question of how *exactly* something works, I just
On Sun, Apr 28, 2019 at 02:07:44AM +0700, Igor Podlesny wrote:
[...]
> Looks like decision made aren't subjects of discussing(?) Well, why
> the hell you have those mail lists then(?) :)
Igor:
The actual purpose of misc@ is for us to learn that you are among the people to
ignore.
Everyone else:
Anonymous writes:
> Otto Moerbeek:
> > On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
> >
> >> Here too: https://www.openbsd.org/65.html
> >
> > Does it matter? It is very common for publications to be dated in the
> > future.
> >
> > -Otto
>
> No, it's not common, neither for
Igor Podlesny writes:
> On Sun, 28 Apr 2019 at 00:59, wrote:
> [...]
> > >
> > > Oh, those hypocrite wankers here and there..
> >
> > If you actually read the code (I know, right? Who DOES that?) you'll see
> > how omalloc_
> init perfectly embarrasses you. In 6.4 it would read the symlink, then
On Sun, Apr 28, 2019 at 02:07:44AM +0700, Igor Podlesny wrote:
> On Sun, 28 Apr 2019 at 00:59, wrote:
> [...]
> > >
> > > Oh, those hypocrite wankers here and there..
> >
> > If you actually read the code (I know, right? Who DOES that?) you'll see
> > how omalloc_init perfectly embarrasses you.
Otto Moerbeek:
> On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
>
>> Here too: https://www.openbsd.org/65.html
>
> Does it matter? It is very common for publications to be dated in the
> future.
>
> -Otto
No, it's not common, neither for software releases nor for texts
On Sun, 28 Apr 2019 at 00:59, wrote:
[...]
> >
> > Oh, those hypocrite wankers here and there..
>
> If you actually read the code (I know, right? Who DOES that?) you'll see how
> omalloc_init perfectly embarrasses you. In 6.4 it would read the symlink,
> then checked the environment, and then
Igor Podlesny writes:
> On Sat, 27 Apr 2019 at 18:09, Marc Espie wrote:
> >
> > On Sat, Apr 27, 2019 at 12:34:01PM +0700, Igor Podlesny wrote:
> > > On Sat, 27 Apr 2019 at 12:26, Sebastien Marie wrote:
> > > > On Sat, Apr 27, 2019 at 12:17:21PM +0700, Igor Podlesny wrote:
> > > > > Previously
attached please find dmesg and backtrace of X when that happen again
hope this bug report will be more useful than previous one.
thank you.
--
With best regards,
Gregory Edigarov
dmesg
Description: Binary data
x.backtrace
Description: Binary data
On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
> Here too: https://www.openbsd.org/65.html
Does it matter? It is very common for publications to be dated in the
future.
-Otto
Here too: https://www.openbsd.org/65.html
On Sat, 27 Apr 2019 at 14:20:32 -, Christian Weisgerber wrote:
> However, as in this example, I think you will only get a few generic
> controls.
>
> It is my theoretical understanding that USB audio gadgets typically
> come with a uhid(4) device, as does yours above, and you would use
>
On 2019-04-27, Levente wrote:
> The headphone in question is the Platronics RIG 500 HD, which connects
> through the USB port (instead of 3.5mm jacks).
> mixerctl output is provided below along with dmesg.
Your headphones, which are really a USB audio adapter with attached
headphones, are a
On Sat, 27 Apr 2019 at 17:55, Stuart Henderson wrote:
[...]
> It is not true. They don't have *wide* support but there is some
> supported hw. If someone wants to change this, I suggest adding acpi
> watchdog support would give the best return for time spent.
Got it.
> Also I don't see what
On Sat, 27 Apr 2019 at 20:38, Vincent Legoll wrote:
>
> On Sat, Apr 27, 2019 at 3:32 PM Igor Podlesny wrote:
> > On Sat, 27 Apr 2019 at 18:09, Marc Espie wrote:
> > > Man, you have some really strange delusions about how to harden things.
> >
> > % man malloc.conf | grep -i security
> > S
On Sat, Apr 27, 2019 at 3:32 PM Igor Podlesny wrote:
> On Sat, 27 Apr 2019 at 18:09, Marc Espie wrote:
> > Man, you have some really strange delusions about how to harden things.
>
> % man malloc.conf | grep -i security
> S Enable all options suitable for security auditing.
>
> Oh,
On Sat, 27 Apr 2019 at 18:09, Marc Espie wrote:
>
> On Sat, Apr 27, 2019 at 12:34:01PM +0700, Igor Podlesny wrote:
> > On Sat, 27 Apr 2019 at 12:26, Sebastien Marie wrote:
> > > On Sat, Apr 27, 2019 at 12:17:21PM +0700, Igor Podlesny wrote:
> > > > Previously users could have different behaviour
On 2019-04-27, Kevin Chadwick wrote:
> How difficult would it be to have a sysupgrade flag to
What sysupgrade and the unattended upgrade do is they automate an
upgrade with ALL DEFAULT settings. Like only pressing enter in the
installer's (U)pgrade mode.
If you want non-defaults, then you
0
C Belgium
P Oost-Vlaanderen
T Dendermonde
Z 9200
O MetaData
I Rolf
A Oliestraat 50
M sa...@metadata.be
U https://metadata.be/
B +32 477 29 76 04
X N/A
N Network consulting, installation and maintenance. Hosting services.
On Sat, Apr 27, 2019 at 01:48:38PM +0100, Kevin Chadwick wrote:
> On 4/25/19 9:27 PM, Christian Weisgerber wrote:
> > ... and this has now been supplanted by /usr/sbin/sysupgrade.
>
> How difficult would it be to have a sysupgrade flag to make the upgrade newfs
> /usr, to save having to rm the
On 4/25/19 9:27 PM, Christian Weisgerber wrote:
> ... and this has now been supplanted by /usr/sbin/sysupgrade.
How difficult would it be to have a sysupgrade flag to make the upgrade newfs
/usr, to save having to rm the files shown in upgrade.html. (I guess it should
work for all users with sane
If you want to be read, configure your email to send normal messages.
All I see is "Signed data", and I'm not necessarily going to open attachments
to see what you're saying on a public mailing-list.
On Sat, Apr 27, 2019 at 12:34:01PM +0700, Igor Podlesny wrote:
> On Sat, 27 Apr 2019 at 12:26, Sebastien Marie wrote:
> > On Sat, Apr 27, 2019 at 12:17:21PM +0700, Igor Podlesny wrote:
> > > Previously users could have different behaviour of malloc simultaneously:
> > > one in
> > > global FS,
On 2019-04-26, Luke A. Call wrote:
> On 04-26 21:47, Rafael Sadowski wrote:
>> []
>> update all packages with the following PKG_PATH example:
>>
>> env PKG_PATH=https://ftp.openbsd.org/pub/OpenBSD/6.5/packages/ pkg_add -u -v
>> -Dinstalled
>>
>> It looks like you mixed packages for 6.4 and
On 2019-04-26, Federico Giannici wrote:
>
> casa:/home/giannici> konsole
> ld.so: konsole: can't load library 'libc++.so.1.0'
> Killed
Running that with LD_DEBUG set in the environment might give a clue.
Likely there will be a lot of output, so have plenty of scrollback buffer,
or use script(1).
On 2019-04-27, Igor Podlesny wrote:
> On Fri, 26 Apr 2019 at 22:58, Stuart Henderson wrote:
>> On 2019-04-26, Igor Podlesny wrote:
>> > Or would kernel's recompiling be needed anyways?
> [...]
>> Recompiling would be needed.
>>
>> If you want to try it, see faq 5 about fetching the source tree,
On 4/27/19 8:23 AM, Otto Moerbeek wrote:
> Additionally, in many cases using a symlink has unclear effects, since
> it is hard to determine if the first malloc call (malloc inits itself
> on first use) happens before of after the chroot call. I would argue
> that in many cases people were thinking
I like reading misc@ mostly due to the constanst BUTTHURT that is going
on here.
But seriously though, each program can change it's own malloc flags
either by calling setenv(3) or just by updating static malloc_options
variable. So there is really *NO* difference between your old way
signature.asc
Description: OpenPGP digital signature
On Fri, Apr 26, 2019 at 11:46:17PM -0600, Theo de Raadt wrote:
> Igor Podlesny wrote:
>
> > On Sat, 27 Apr 2019 at 12:37, Anthony J. Bentley wrote:
> > >
> > > You didn't check the manpage.
> >
> > you didn't think it over.
> > https://www.mail-archive.com/misc@openbsd.org/msg167012.html
>
>
On Sat, 27 Apr 2019 at 12:55, Theo de Raadt wrote:
> Igor Podlesny wrote:
> > On Sat, 27 Apr 2019 at 12:37, Anthony J. Bentley wrote:
> > > You didn't check the manpage.
> >
> > you didn't think it over.
> > https://www.mail-archive.com/misc@openbsd.org/msg167012.html
>
> Igor, talking back to
39 matches
Mail list logo