With the changes in 5.6 using sendsyslog(2), only syslogd picks up
local syslog. Search the openbsd-ports list for syslog-ng to see some
comments on it.
I have a similar sort of setup during installs and I clear out the
first 10m before setting up the CRYPTO disk and it works for me. I
don't think you're zeroing out enough at the beginning of the disk.
dd if=/dev/zero of=/dev/rsd0c bs=10m count=1
On Tue, Dec 1, 2015 at 4:33 PM, Patrik Lundin wro
On Fri, Nov 13, 2015 at 4:37 PM, szs wrote:
> I have been playing around with auto_install today, hugely satisfying seeing
> your system install in less than two mins!
>
> I wondering if anyone has any experience mixing this with disk encryption with
> bioctl?
>
> I'm thinking that it may take som
I ran into this exact same issue when I was trying to create a
rollback install with CRYPTO for a sort of appliance I develop/manage
for my company. We only have remote access with console and remote
hands aren't easy to get so when upgrading it'd be nice to have a
rollback in case something happen
Try changing the value for the sysctl variable
"kern.timecounter.hardware"? Its just a guess, but its helped me when
I had problems with the clock before.
On Fri, Jan 2, 2015 at 7:47 AM, John Merriam wrote:
> Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320. The
> clock doesn'
I'm trying to create an appliance like install and want to stop
logging to console. So this is during the install process, not a
normally running machine. I know this is very useful information, but
this would definitely be nice to disable for a bit.
In particular when running bioctl to setup a so
Tim, I didn't even think about just using another disk. That's the
simpler solution by far, but does come with some drawbacks. A very
small partition or disk by itself is pretty conspicuous, and wouldn't
be very hard to figure out what its for.
It also does make our install a bit more complex. We
Eric, thats an interesting way to do it. Though I think it would take
more changes in the system than we'd like to implement.
I was actually able to get full disk encryption to work without
entering the passphrase. I edited softraid.c
(http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/sta
s eyes, I don't need to stop
someone really determined.
I just want to make sure there isn't some standard way to obfuscate
partitions/data in VMs used as appliances.
On Tue, Dec 9, 2014 at 11:38 AM, John Merriam wrote:
> On Tue, 9 Dec 2014, Nathan Wheeler wrote:
>
>> Hi eve
Hi everyone,
We use OpenBSD currently on physical hardware and manage it in our
customers location. We want the option to give out VMs to host on
customer premises and we'll still manage the VM (but not the VM
platform).
The problem is not letting the customer access to our proprietary data
as th
10 matches
Mail list logo
