Hi Stefan.
Thanks that worked.
> On 24 May 2020, at 16:46, Stefan Sperling wrote:
>
> On Sun, May 24, 2020 at 03:08:09PM +0200, Hendrik Meyburgh wrote:
>>> Synopsis: ral interface is not working
>>> Category: system
>>> Environment:
>> System : OpenBSD 6.7
>> Details : Op
On Mon, May 25, 2020 at 04:15:24PM -0600, Todd C. Miller wrote:
> On Mon, 25 May 2020 16:04:25 -0600, Bob Beck wrote:
>
> > getlock()'s behaviour changes in the case of a writeable mail spool. if we
> > want to keep supporting this, I we can modify the pledge as follows:
>
> I thought we decided
On Mon, 25 May 2020 16:04:25 -0600, Bob Beck wrote:
> getlock()'s behaviour changes in the case of a writeable mail spool. if we
> want to keep supporting this, I we can modify the pledge as follows:
I thought we decided not to adjust the pledge when I brought it up
last time. Here's the diff I
On Mon, May 25, 2020 at 04:05:47PM -0600, Theo de Raadt wrote:
> > + if (pledge("id flock stdio rpath wpath getpw cpath fattr", NULL) ==
> > -1)
>
> Please wait for other pledge people to respond.
>
> But re-order. Add the new things to the end.
>
Ack
> + if (pledge("id flock stdio rpath wpath getpw cpath fattr", NULL) ==
> -1)
Please wait for other pledge people to respond.
But re-order. Add the new things to the end.
On Mon, May 25, 2020 at 11:07:12PM +0200, Dawid Czelu??niak wrote:
> After changing permissions of /var/mail directory to 755:
>
> $ chmod 755 /var/mail
>
> everything is fine and seteuid(2) is not called:
> 92121 lockspool NAMI "/var/mail/root.lock"
> 92121 lockspool RET unlink 0
> 92121 l
On Sat, May 23, 2020 at 9:57 AM Stefan Sperling wrote:
> On Fri, May 22, 2020 at 05:12:23PM +0200, stolen data wrote:
> > On Thu, May 21, 2020 at 9:11 AM Stefan Sperling wrote:
> >
> > > On Thu, May 21, 2020 at 01:04:36AM +0200, stolen data wrote:
> > >
> > > ...
> > >
> >
> > > > > You can tr
After changing permissions of /var/mail directory to 755:
$ chmod 755 /var/mail
everything is fine and seteuid(2) is not called:
92121 lockspool NAMI "/var/mail/root.lock"
92121 lockspool RET unlink 0
92121 lockspool CALL kbind(0x7f7c7f58,24,0xefbb72852ff02523)
92121 lockspool RET k
Hi,
I noticed that when I try to run /usr/libexec/lockspool directly as root
I'm getting Abort trap on my machine:
$ /usr/libexec/lockspool
Abort trap
$ echo $?
134
And in dmesg I can see plenty of pledge logs:
lockspool[73511]: pledge "id", syscall 183
lockspool[94755]: pledge "id", syscall 183
Kevin Chadwick(m8il1i...@gmail.com) on 2020.05.25 11:57:44 +:
> . did you ever saw something like this? for instance when you
> >want to upgrade java, is says: open-jre 14 does not exist.
> >
>
> I'm not an OpenBSD dev but are you asking for a more user friendly message
> ratter than a more pe
This conversation is finished.
Move along.
Andreas Kusalananda =?utf-8?B?S8OkaMOkcmk=?= wrote:
> On Mon, May 25, 2020 at 02:22:42PM +0100, Stuart Henderson wrote:
> > On 2020/05/25 14:46, Andreas Kusalananda Kähäri wrote:
> > > On Mon, May 25, 2020 at 12:26:25PM +, abed wrote:
> > > > I'
On Mon, May 25, 2020 at 02:22:42PM +0100, Stuart Henderson wrote:
> On 2020/05/25 14:46, Andreas Kusalananda Kähäri wrote:
> > On Mon, May 25, 2020 at 12:26:25PM +, abed wrote:
> > > I'm expecting when the 6.8 dosen't exist, we have to show a message not
> > > an error (404 not found )!!!
> > >
On 5/25/20 1:57 PM, Kevin Chadwick wrote:
. did you ever saw something like this? for instance when you
want to upgrade java, is says: open-jre 14 does not exist.
I'm not an OpenBSD dev but are you asking for a more user friendly message
ratter than a more pertinent one? Seems reasonable,
I have reverted the patch. Let's see if I could somehow reproduce
the problem myself so I can study it.
On Mon, May 25, 2020 at 03:21:01PM +0100, Stuart Henderson wrote:
> visa pointed me at sys/kern/kern_event.c r1.132 as a possibility -
> I reverted that yesterday and haven't seen the system ha
visa pointed me at sys/kern/kern_event.c r1.132 as a possibility -
I reverted that yesterday and haven't seen the system hang yet.
That's not conclusive but considering how things were going before,
I think it would have happened by now.
On 2020/05/23 23:41, Stuart Henderson wrote:
> I have some
Yes that right, but how but to make convenience for everybody at least
once? everybody can change the script but i talked about something higher.
On 5/25/20 1:19 PM, Peter N. M. Hansteen wrote:
> On Mon, May 25, 2020 at 01:07:23PM +, abed wrote:
>> How about if next version doesn't exist?
> Pl
yes, this is exactly what we call a program, we to check them all. if
exist or not. if we mirror is visible or not. if exist but corrupted. so
we need a common criteria.
On 5/25/20 1:22 PM, Stuart Henderson wrote:
> On 2020/05/25 14:46, Andreas Kusalananda Kähäri wrote:
>> On Mon, May 25, 2020 at
On 2020/05/25 14:46, Andreas Kusalananda Kähäri wrote:
> On Mon, May 25, 2020 at 12:26:25PM +, abed wrote:
> > I'm expecting when the 6.8 dosen't exist, we have to show a message not
> > an error (404 not found )!!!
> >
> > On 5/25/20 12:21 PM, Stuart Henderson wrote:
> > > On 2020/05/25 11:33
On Mon, May 25, 2020 at 01:07:23PM +, abed wrote:
> How about if next version doesn't exist?
Please read the previous answers and the sysupgrade man page, or for that
matter /usr/sbin/sysupgrade itself - it's a very readable shell script.
OpenBSD 6.8 does not exist yet. sysupgrade told you s
Yeah exactly, finally somebody got the point!!!
On 5/25/20 12:46 PM, Andreas Kusalananda Kähäri wrote:
> On Mon, May 25, 2020 at 12:26:25PM +, abed wrote:
>> I'm expecting when the 6.8 dosen't exist, we have to show a message not
>> an error (404 not found )!!!
>>
>> On 5/25/20 12:21 PM, Stuar
How about if next version doesn't exist?
On 5/25/20 12:42 PM, Peter N. M. Hansteen wrote:
> On Mon, May 25, 2020 at 11:47:33AM +, abed wrote:
>> I'm exactly talking about the logic behind. basically it's not aware of
>> the latest version and only increments the minor (6.7+0.1) and try to
>> d
On Mon, May 25, 2020 at 12:26:25PM +, abed wrote:
> I'm expecting when the 6.8 dosen't exist, we have to show a message not
> an error (404 not found )!!!
>
> On 5/25/20 12:21 PM, Stuart Henderson wrote:
> > On 2020/05/25 11:33, abed wrote:
> >> After installing OpenBSD 6.7 (i mean exactly aft
On Mon, May 25, 2020 at 11:47:33AM +, abed wrote:
>
> I'm exactly talking about the logic behind. basically it's not aware of
> the latest version and only increments the minor (6.7+0.1) and try to
> download. did you ever saw something like this? for instance when you
> want to upgrade java,
$ man sysupgrade | grep -i smart
$
I see no such promise.
On Mon, 2020-05-25 at 12:07 +, abed wrote:
> OK, but it supposed to be more smart !!!
>
> On 5/25/20 12:02 PM, Renaud Allard wrote:
> >
> > On 5/25/20 1:57 PM, Kevin Chadwick wrote:
> > > . did you ever saw something like this? for i
Stuart, this all about polishing the code. believe me this is not
reasonable nor brainier.
On 5/25/20 12:21 PM, Stuart Henderson wrote:
> On 2020/05/25 11:33, abed wrote:
>> After installing OpenBSD 6.7 (i mean exactly after that without touching
>> a thing). if you issue sysupgrade, it says: cant
I'm expecting when the 6.8 dosen't exist, we have to show a message not
an error (404 not found )!!!
On 5/25/20 12:21 PM, Stuart Henderson wrote:
> On 2020/05/25 11:33, abed wrote:
>> After installing OpenBSD 6.7 (i mean exactly after that without touching
>> a thing). if you issue sysupgrade, it
On 2020/05/25 11:33, abed wrote:
>
> After installing OpenBSD 6.7 (i mean exactly after that without touching
> a thing). if you issue sysupgrade, it says: cant find version 6.8, which
> is absolutely doesn't exist. I wondering is it really hard to firs check
> the latest version when we heavily c
OK, but it supposed to be more smart !!!
On 5/25/20 12:02 PM, Renaud Allard wrote:
>
>
> On 5/25/20 1:57 PM, Kevin Chadwick wrote:
>> . did you ever saw something like this? for instance when you
>>> want to upgrade java, is says: open-jre 14 does not exist.
>>>
>>
>> I'm not an OpenBSD dev but ar
I bet you didn't get the point. it's not about user friendly it's about
accuracy. if you want to write a script to check the repository you cant
find out the issue is about your connection or about anything else. yeah
also better than my bike!!
On 5/25/20 11:57 AM, Kevin Chadwick wrote:
> . did yo
. did you ever saw something like this? for instance when you
>want to upgrade java, is says: open-jre 14 does not exist.
>
I'm not an OpenBSD dev but are you asking for a more user friendly message
ratter than a more pertinent one? Seems reasonable, but when I got that
message. I actually wante
I'm exactly talking about the logic behind. basically it's not aware of
the latest version and only increments the minor (6.7+0.1) and try to
download. did you ever saw something like this? for instance when you
want to upgrade java, is says: open-jre 14 does not exist.
On 5/25/20 11:37 AM, Sole
Le Mon, 25 May 2020 11:33:10 +,
abed a écrit :
> After installing OpenBSD 6.7 (i mean exactly after that without
> touching a thing). if you issue sysupgrade, it says: cant find
> version 6.8, which is absolutely doesn't exist. I wondering is it
> really hard to firs check the latest version
After installing OpenBSD 6.7 (i mean exactly after that without touching
a thing). if you issue sysupgrade, it says: cant find version 6.8, which
is absolutely doesn't exist. I wondering is it really hard to firs check
the latest version when we heavily connected to the web from seconds we
boot o
On 25/05/20(Mon) 12:56, Gerhard Roth wrote:
> On 5/22/20 9:05 PM, Mark Kettenis wrote:
> > > From: Łukasz Lejtkowski
> > > Date: Fri, 22 May 2020 20:51:57 +0200
> > >
> > > Probably power supply 12 V is broken. Showing 16,87 V(Fluke 179) -
> > > too high. Should be 12,25-12,50 V. I replaced to th
On 5/22/20 9:05 PM, Mark Kettenis wrote:
From: Łukasz Lejtkowski
Date: Fri, 22 May 2020 20:51:57 +0200
Probably power supply 12 V is broken. Showing 16,87 V(Fluke 179) -
too high. Should be 12,25-12,50 V. I replaced to the new one.
That might be why the device stops responding. The fact that
35 matches
Mail list logo