> Maybe it's a CPU related bug, who knows.
Maybe you are using powerpc or arch64 and your bug isn't reproducible on amd64.
No, the CPU is an amd64. It is was something else, I would have mentioned it.
> There is a page explaining how to report bug properly
> https://www.openbsd.org/report.html
On 2020/05/04 23:03, Rupert Gallagher wrote:
> > Maybe it's a CPU related bug, who knows.
> Maybe you are using powerpc or arch64 and your bug isn't reproducible on
> amd64.
>
> No, the CPU is an amd64. It is was something else, I would have mentioned it.
You aren't going to get accurate
On 2020/05/04 22:57, Rupert Gallagher wrote:
> > So you don't think there could be something odd in the bsd.rd so you would
> > write
> "download bsd.rd #234234 from ftp.unsynchedmirror.com or my copy here"
> Perhaps this was fixed in 6.5 and you are running something older?
>
> Why bothering
For OpenBSD 6.6, amd64
in the daily script to check security:
/usr/libexec/security
at line 248 for checking if the umask is set:
my @list = qw(/etc/profile /root/.profile);
shouldn't that be instead:
my @list = qw(/.profile /root/.profile);
I think /etc/profile does not exist, and /.profile
On Mon, May 04, 2020 at 06:24:49PM +0200, Klemens Nanni wrote:
> On Mon, May 04, 2020 at 05:49:26PM +0300, bsdlis...@gmail.com wrote:
> > Say I have a SSID like "Mike's". If I set it up at install time, at the
> > first boot /etc/netstart will fail with an unmatched quote error. Attached
> >
On Mon, May 04, 2020 at 05:49:26PM +0300, bsdlis...@gmail.com wrote:
> Say I have a SSID like "Mike's". If I set it up at install time, at the
> first boot /etc/netstart will fail with an unmatched quote error. Attached is
> the generated /etc/hostname.iwn0 file as generated. If I change
please see the attached file as generated by sendbug
>Synopsis: /etc/netstart fails with "'"s in the SSID
>Category: system
>Environment:
System : OpenBSD 6.7
Details : OpenBSD 6.7-beta (GENERIC.MP) #172: Sun May 3 09:43:47
MDT 2020
Hi Stuart,
very preliminary answer off the top of my head:
Stuart Henderson wrote on Mon, May 04, 2020 at 04:23:44PM +0100:
> On 2020/05/04 15:01, Doug Moss wrote:
>> For OpenBSD 6.6, amd64
>> in the daily script to check security:
>> /usr/libexec/security
>>
>> at line 248 for checking if the
On Mon, May 04, 2020 at 04:23:44PM +0100, Stuart Henderson wrote:
> On 2020/05/04 15:01, Doug Moss wrote:
> > For OpenBSD 6.6, amd64
> > in the daily script to check security:
> > /usr/libexec/security
> >
> > at line 248 for checking if the umask is set:
> > my @list = qw(/etc/profile
On 2020/05/04 15:01, Doug Moss wrote:
> For OpenBSD 6.6, amd64
> in the daily script to check security:
> /usr/libexec/security
>
> at line 248 for checking if the umask is set:
> my @list = qw(/etc/profile /root/.profile);
>
> shouldn't that be instead:
> my @list = qw(/.profile
> dmesg, bsd.rd version, hw info? Missing
HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw works very
well with obsd, and the crash occurred when *I* was mounting a disk image.
> Steps to repro? Missing
I assume bug@ knows how to mount a disk image.
> The page
Le Mon, 04 May 2020 10:11:02 +,
Rupert Gallagher a écrit :
> > dmesg, bsd.rd version, hw info? Missing
>
> HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw
> works very well with obsd, and the crash occurred when *I* was
> mounting a disk image.
Maybe it's a CPU related
12 matches
Mail list logo
