Hi,
On Wed, Oct 11, 2017, at 12:28, Eric Furman wrote:
>
> I disagree, but that's just my opinion.
> And just because something is "a default BIOS configuration in all
> modern
> desktop computers" doesn't mean it's a good thing.
>
To add another case point, at least on his system (HP Z230)
On Tue, Oct 10, 2017, at 04:29 PM, Rostislav Krasny wrote:
> I think it's worth to be supported. The RAID mode of storage
> controller seems to be a default BIOS configuration in all modern
> desktop computers. I think most desktop users don't configure any real
> RAID and continue to use their
Thank you for your answer!
On 6 oct. 2017 à 20:13 +0200, Theo de Raadt , wrote:
> > I'm trying to use pledge to protect a go program.
> >
> > The exec aborts with abort trap: core dump
> >
> > Ktrace and /var/log/messages say that the __set_tcb
> > syscall is denied.
> >
> >
On Mon, Oct 09, 2017 at 06:31:06PM +, lists+m...@ggp2.com wrote:
> Hello all -
>
> I don't feel this warrants a bug report, but nevertheless feel that this
> behavior is inconsistent with the way dhclient works. I have a vultr
there is a school of thought that says dhclient should not delay
I think it's worth to be supported. The RAID mode of storage
controller seems to be a default BIOS configuration in all modern
desktop computers. I think most desktop users don't configure any real
RAID and continue to use their disks as separate devices. If at least
this RAID configuration is
On Tue, Oct 10, 2017 at 08:08:56PM +0200, Tony Sarendal wrote:
> Not looking so good.
>
> tonsar@jump0.swe1$ ftp ftp.eu.openbsd.org
> Trying 193.156.26.18...
> Connected to ftp.eu.openbsd.org (193.156.26.18).
> 220 jj-prod-obsdmirror.inet6.se FTP server ready.
> Name (ftp.eu.openbsd.org:tonsar):
On 10/10/17 11:57, Roar Waagsbø wrote:
> Hi.
>
> Sorry.
>
> Its my first report.
>
> Im not even sure its a bug or if its me doing something wrong.
>
> The logs arent saying much either, besides the one line I posted.
>
> Roar
>
> On Oct 10, 2017 5:21 PM, "Mike Larkin"
This is kind of intentional, since noone has put effort into making
softraid understand the disk-binding logic found in the BIOS-RAID
sectors. Maybe we should reconsider, dunno.
> I've just tried to install the amd64 OpenBSD 6.2 and it doesn't see
> hard disks when controller in RAID mode (BIOS
Hi.
Sorry.
Its my first report.
Im not even sure its a bug or if its me doing something wrong.
The logs arent saying much either, besides the one line I posted.
Roar
On Oct 10, 2017 5:21 PM, "Mike Larkin" wrote:
> On Tue, Oct 10, 2017 at 02:39:05PM +0200, Roar Waagsbř
Not looking so good.
tonsar@jump0.swe1$ ftp ftp.eu.openbsd.org
Trying 193.156.26.18...
Connected to ftp.eu.openbsd.org (193.156.26.18).
220 jj-prod-obsdmirror.inet6.se FTP server ready.
Name (ftp.eu.openbsd.org:tonsar): ftp
331 Guest login ok, send your email address as password.
Password:
230
On Wed, 27 Sep 2017 21:43:48 -0500
> Why is this happening, and is there anything that I should do to
> correct
>
The system has been getting more and more dynamic to make attackers
fumble in the dark.
> the "Permission denied" error?
If you prefer then add:
/sbin/mount -uo noexec /tmp
Hi,
I've just tried to install the amd64 OpenBSD 6.2 and it doesn't see
hard disks when controller in RAID mode (BIOS configuration). If I
change it to AHCI mode (in BIOS) it can see them.
Although I don't use RAID capabilities I can't switch to the AHCI mode
because I have Windows 7 installed
On Tue, Oct 10, 2017 at 02:39:05PM +0200, Roar Waagsbø wrote:
> Hi.
>
> I starting using openbsd a while back and I was told on #openbsd@freenode
> that vmm was the way to go, and not use qemu.
>
> I want to use openbsd on my host machine.
>
> I setup two vms and it worked fine.
>
> After
Hello,
Since the upgrade to OpenBSD 6.2 (from 6.1). One of my tunnels is not
working anymore (it was working on 6.1)
There are 2 things which differ from the other (working) ones:
Both hosts are natted, and one host is i386 (instead of amd64).
I can see packets leaving the source server and
On Tue, Oct 10, 2017 at 11:13:45PM +1100, tomr wrote:
> Well... there's nothing in the FAQ about using a keydisk at all, and
> there's no hints in bioctl(8) about using both a keydisk and a password
> together.
That's because using both isn't a supported use case yet.
In the current design and
Hi.
I starting using openbsd a while back and I was told on #openbsd@freenode
that vmm was the way to go, and not use qemu.
I want to use openbsd on my host machine.
I setup two vms and it worked fine.
After about a week I noticed that one of my vms was shutdown.
I started it back up again
On 09/28/17 17:58, Stefan Sperling wrote:
> On Thu, Sep 28, 2017 at 04:15:20AM +0200, Erling Westenvik wrote:
>> On Thu, Sep 28, 2017 at 09:11:49AM +1000, tomr wrote:
>>> I remember seeing a post, I think on undeadly.org, which went through
>>> having the bootloader on password-encrypted usb
On Mon, Oct 09, 2017 at 08:03:54PM -0500, Daniel Boyd wrote:
> I’ve just started a job where I will be working from home a bunch, so I would
> like to configure my home router as an ipsec/l2tp client and to push the
> routes from my work network to all computers on my home network. i.e. a
>
On 2017-10-10, Daniel Boyd wrote:
> I’ve just started a job where I will be working from home a bunch, so I would
> like to configure my home router as an ipsec/l2tp client and to push the
> routes from my work network to all computers on my home network. i.e. a
>
On 2017-10-09, Todd C. Miller wrote:
> On Mon, 09 Oct 2017 17:24:53 +0200, Max Power wrote:
>
>> Hi guys, and wishes for the new release, Thank You Theo.
>>
>> Installing gtar ask me:
>> Ambiguos: choose package for gtar
>> a 0:
>> 1: gtar-1.28p1
>>
On Tue, Oct 10, 2017, at 10:22, leo_...@volny.cz wrote:
> Instead of sd0b? Then it appears fine.
Yes, that was my point, everything seemed fine until I found that line
in dmesg.
> >> You might want to keep sd0b around as a dump partition though, just in
> >> case it ever panics before going
Haai,
"Frank Groeneveld" wrote:
>
> swapctl -l always lists /dev/sd1b correctly.
Instead of sd0b? Then it appears fine.
>> You might want to keep sd0b around as a dump partition though, just in
>> case it ever panics before going multiluser...
>
> The point of this
On Tue, Oct 10, 2017, at 09:48, leo_...@volny.cz wrote:
> It'd seem more wrong to me if it'd try to swap to a nonexistent
> partition ;) Just in case, what is the output of 'swapctl -l' straight
> after boot, preferably when still single-user?
swapctl -l always lists /dev/sd1b correctly.
> You
Hi misc,
I have a PC Engines apu2b4 with one 16 GB
ssd, for installation or reboot reasons I am
connected via serial console.
Here is the boot screen:
(dmesg below)
=
PC Engines apu2
coreboot build 20170831
BIOS version v4.0.12
4080 MB ECC DRAM
SeaBIOS (version
Haai,
"Frank Groeneveld" wrote:
> I recently switched the swap partition on a server from sd0b to sd1b.
> I've modified /etc/fstab accordingly and after a reboot swapctl -l lists
> it as being the only used swap partition correctly. Today I noticed this
> line in dmesg:
I recently switched the swap partition on a server from sd0b to sd1b.
I've modified /etc/fstab accordingly and after a reboot swapctl -l lists
it as being the only used swap partition correctly. Today I noticed this
line in dmesg:
root on sd0a (4340b9bfa4cdde0a.a) swap on sd0b dump on sd0b
It
On 09/28/2017 06:34 AM, Philip Guenther wrote:
> On Wed, 27 Sep 2017, Theodore Wynnychenko wrote:
> ...
>> Thank you for the information. I removed the “noexec” flag from fstab
>> and the error has disappeared.
>>
>> But, I am also surprised by the requirement that /tmp _not_ be mounted
>>
27 matches
Mail list logo