On Wed, May 04, 2016 at 06:58:32AM +0200, Otto Moerbeek wrote:
> On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote:
>
> > Thanks for your advice, however it makes no difference changing login.conf
> > in the way you mentioned.. Still errors out and core dumps.
> > Root can't get access to it
On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote:
> Thanks for your advice, however it makes no difference changing login.conf in
> the way you mentioned.. Still errors out and core dumps.
> Root can't get access to it now either. Here's my login.conf, I changed the:
>
>
On 12/29, Gabriel Guzman wrote:
> I've been seeing a similar issue on a DELL XPS 13" Developer edition I got
> back in June -- ran fine with ubuntu as shipped with Dell, and then I
> wiped and installed OpenBSD and now can't even access the BIOS.
I figured out the issue. On my machine (DEL
> The random(4) device on FreeBSD will block until the generator is
> seeded [0], but not after, unless kern.random.sys.seeded is changed.
>
> Is this the case for getentropy(2) or random(4) on OpenBSD, and if
> not, would it be a good idea to make it do so?
>
> [0]
The random(4) device on FreeBSD will block until the generator is
seeded [0], but not after, unless kern.random.sys.seeded is changed.
Is this the case for getentropy(2) or random(4) on OpenBSD, and if
not, would it be a good idea to make it do so?
[0]
On Tue, May 3, 2016 at 9:21 PM, Ted Unangst wrote:
> Aioi Yuuko wrote:
>> Why is MAXINTERP in only 128? I can think of a few:
>>
>> 1. It's been that way a while and nobody's complained
>> 2. If someone's shebangs are longer than that, they're probably doing
>> whatever
Aioi Yuuko wrote:
> Why is MAXINTERP in only 128? I can think of a few:
>
> 1. It's been that way a while and nobody's complained
> 2. If someone's shebangs are longer than that, they're probably doing
> whatever they're doing horribly, horribly wrong
> 3. Historical compatibility
>
> Is it
Thanks for your advice, however it makes no difference changing login.conf in
the way you mentioned.. Still errors out and core dumps.
Root can't get access to it now either. Here's my login.conf, I changed the:
:openfiles-cur=2048:\
:openfiles-max=4096:\
on my staff group as well, for which
Why is MAXINTERP in only 128? I can think of a few:
1. It's been that way a while and nobody's complained
2. If someone's shebangs are longer than that, they're probably doing whatever
they're doing horribly, horribly wrong
3. Historical compatibility
Is it one of those? If not, is it
On Tue, May 03, 2016 at 03:32:34PM -0500, Chase Davis wrote:
> Mike,
>
> We took your suggestion and re-wrote the driver to model sdhc_acpi. I
> have attached the new code. However, the match function never returns
> a 1. We put temporary print statements in the match routine. It is
> being
On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote:
> The owncloudclient refuses to work and core dumps on non-root user
> Works but throws out warnings on root.. although I feel a little edgy running
> this client as root.
>
> Application: owncloudclient
> System: 5.9 Stable
>
>
Mike,
We took your suggestion and re-wrote the driver to model sdhc_acpi. I
have attached the new code. However, the match function never returns
a 1. We put temporary print statements in the match routine. It is
being called several times during the kernel boot process, but it
never finds a
The owncloudclient refuses to work and core dumps on non-root user
Works but throws out warnings on root.. although I feel a little edgy running
this client as root.
Application: owncloudclient
System: 5.9 Stable
###
$ owncloud
(owncloud:30815): GLib-ERROR **: Creating pipes for
I have been having these issues with owncloud on 5.9 Stable where I will go to
log in and says password is wrong, I have two set ups - one in the cloud and
one at home, both are randomly doing this. My partner had to change password 8
times last night before it would actually work on next log
A separate question about combining mmap access and file
IO in the current absence of a unified buffer cache:
If I have a readonly mmap and do fwrite to it, could I use
fsync (or msync or any other call) right after the fwrite, as a tool to
guarantee that the memory mapping interface is up to
On Tue, 03 May 2016 02:53:36 -0600
Theo de Raadt wrote:
> mfs is reliable.
> tmpfs has bugs, and as a result of those bugs, it has fewer and fewer
> users.
> Or, maybe there are fewer problem reports because fewer people use
> it, because those who tried to use it ran
I actually wrote a patch to that a while back, and it was not accepted.
Looking back, I am not disappointed that it was rejected, and it forced
me to find another solution: shell scripts, included below.
However, in light of what Theo said, I'm possibly going to move back to
mfs; even if I
Building 5.9 machines to replace 5.5 ones. Looking in /usr/src on the 5.9
machines, I do not see the code for rwhod. Has this been removed, and if
so, why? We use this on all of our mahcines.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a
On Tue, May 03, 2016 at 05:08:06PM +1000, bytevolc...@safe-mail.net wrote:
> With tmpfs being in the tree for the last 2+ years (since OpenBSD 5.5),
> I would like to ask, besides the "-P" option in mount_mfs, what is the
> advantage of using mfs over tmpfs?
tmpfs on Bitrig does support
> With tmpfs being in the tree for the last 2+ years (since OpenBSD 5.5),
> I would like to ask, besides the "-P" option in mount_mfs, what is the
> advantage of using mfs over tmpfs?
mfs is reliable.
> It seems tmpfs has the following advantages:
>
> - Can grow or shrink; shrinks when files
Hello,
With tmpfs being in the tree for the last 2+ years (since OpenBSD 5.5),
I would like to ask, besides the "-P" option in mount_mfs, what is the
advantage of using mfs over tmpfs?
It seems tmpfs has the following advantages:
- Can grow or shrink; shrinks when files are erased.
- Can
On 03 May 2016, Anthony Campbell wrote:
> On 02 May 2016, Mike Larkin wrote:
> > On Sun, May 01, 2016 at 04:08:28PM +0100, Anthony Campbell wrote:
> > > This is on a Thinkpad Z61m running amd64. Suspend on lid closure has
> > > worked without problems for many months with numerous snapshots. After
On 02 May 2016, Mike Larkin wrote:
> On Sun, May 01, 2016 at 04:08:28PM +0100, Anthony Campbell wrote:
> > This is on a Thinkpad Z61m running amd64. Suspend on lid closure has
> > worked without problems for many months with numerous snapshots. After
> > upgrading on 30 April the machine no longer
23 matches
Mail list logo