On February 13, 2015 2:19:05 AM CET, Dutch Ingraham wrote:
>Hello all:
>
>I installed the binary mutt last week with the compressed, sasl, and
>sidebar
>flavors. I also used my standard .muttrc from other systems.
>Everything
>worked fine except the sidebar. While all folders are present, and I
Hi,
I'd say its way easier to help you and debug it with your .muttrc-file. I'm
using sidebar
with mutt and have no issues with it.
Send both mutt -v output and .muttrc
Cheers,
Alexander
On 2015-02-12 20:19:05, Dutch Ingraham wrote:
> Hello all:
>
> I installed the binary mutt last week with
Hi, Just an update.
I continue with the lag. So I decided to try other players, and I discovered
that ffplay from ffmpeg don't lag, this is the only one I found that works, with
both audio and video. But the problem isn't solved yet since I like cmus and
mplayer and I wanna use them. This is real
On Tue, Jan 13, 2015 at 4:58 AM, Daniel Cegiełka
wrote:
> http://www.openwall.com/lists/oss-security/2015/01/07/5
>
> Does someone can confirm this vulnerability? It's probably the problem
> of "OpenBSD-derived (?) pax".
Thanks for bringing this to our attention!
After much thrashing around, I b
Hello all:
I installed the binary mutt last week with the compressed, sasl, and sidebar
flavors. I also used my standard .muttrc from other systems. Everything
worked fine except the sidebar. While all folders are present, and I can
scroll to any folder, no folder will open. The folders do see
Hi,
just a reminder - we'll have our "Hannover BSD meetup" next week.
And due to the positive feedback, I would appreciate if you'd
optionally drop me a private note if you're intending to attend.
We'll have some users and OpenBSD developers joining us. The people
at the bar got concerned when w
On 2015-02-12 10:18, Stuart Henderson wrote:
> On 2015-02-11, Hugo Osvaldo Barrera wrote:
> > Can
> > someone else confirm postgres9.4 work fine on the latest -snapshot? (the
> > confirmation would be helpful to reafirm that it's not an issue with some
> > dependency or library).
>
> Works fine on
On Feb 12 19:20:05, schwa...@usta.de wrote:
> Jan Stary wrote on Thu, Feb 12, 2015 at 02:52:33PM +0100:
>
> > I have some man pages installed in $HOME/man
> > so I augment my manpath like this in my ~/.shrc
> >
> > test -d $HOME/man && alias man="man -m $HOME/man"
> >
> > Now man(1) complains
Hi Jan,
Jan Stary wrote on Thu, Feb 12, 2015 at 02:52:33PM +0100:
> I have some man pages installed in $HOME/man
> so I augment my manpath like this in my ~/.shrc
>
> test -d $HOME/man && alias man="man -m $HOME/man"
>
> Now man(1) complains saying
>
> $ man ls
> man: -m/home/hans/man: B
Hi,
Jan Stary wrote:
Perhaps this is intended; does it mean that once the battery gets
to a capacity of 1Wh, then having it charged to 1Wh will be a "full"
battery? Would it be better if apm -l said the battery is
(14.75 / 48.84) full now?
Exctly that. At each cycle, every battery, but especia
Ok, I don't know how this is controled, but the problem is, you are
actually running mandoc for which, -m means something different. I am
running actual man, I guess.
I just updated -current this morning (snapshot from 2/10) so I don't
know what the difference is.
On 2/12/15, John Merriam wrote:
> On Thu, 12 Feb 2015, Jan Stary wrote:
>> On Feb 12 11:12:46, j...@johnmerriam.net wrote:
>> > On 2015-02-12 10:50, Jan Stary wrote:
>> > >On Feb 12 10:15:08, j...@johnmerriam.net wrote:
>> > >>What does it show when you run the alias command with no arguments to
>
On Thu, 12 Feb 2015, Jan Stary wrote:
> On Feb 12 11:12:46, j...@johnmerriam.net wrote:
> > On 2015-02-12 10:50, Jan Stary wrote:
> > >On Feb 12 10:15:08, j...@johnmerriam.net wrote:
> > >>What does it show when you run the alias command with no arguments to
> > >>display your current aliases?
> >
On Feb 12 11:29:18, tro...@gmail.com wrote:
> Do you have another man installed somewhere?
No.
> $ man -V
> mandoc 1.13.2
Yes.
Do you have another man installed somewhere?
$ man -V
mandoc 1.13.2
On Feb 12 11:12:46, j...@johnmerriam.net wrote:
> On 2015-02-12 10:50, Jan Stary wrote:
> >On Feb 12 10:15:08, j...@johnmerriam.net wrote:
> >>What does it show when you run the alias command with no arguments to
> >>display your current aliases?
> >>
> >>I noticed that in the error message there i
On 02/12/15 10:10, Boris Goldberg wrote:
> Hello Nick,
...
> I was entertaining the idea of making a 100 TB OpenBSD based archive
> storage, even asked the list. The only answer pointed to that FAQ page, and
> it stopped me from pursuing that idea. Servers with 128 GB of RAM aren't
> uncommon, bu
On Thu, 12 Feb 2015, Jan Stary wrote:
> I have some man pages installed in $HOME/man
> so I ugment my manpath like this in my ~/.shrc
>
> test -d $HOME/man && alias man="man -m $HOME/man"
>
> Now man(1) complains saying
>
> $ man ls
> man: -m/home/hans/man: Bad argument
>
> Using "$HOME/
Hello Nick,
Wednesday, February 11, 2015, 1:05:20 PM, you wrote:
NH> On 02/11/15 11:58, Jan Stary wrote:
>> On Feb 10 17:48:22, na...@mips.inka.de wrote:
>>> On 2015-02-10, yary wrote:
>>>
I know FFS2 can handle that size easily, but I'm worried about fsck
taking forever. This machine
I have some man pages installed in $HOME/man
so I ugment my manpath like this in my ~/.shrc
test -d $HOME/man && alias man="man -m $HOME/man"
Now man(1) complains saying
$ man ls
man: -m/home/hans/man: Bad argument
Using "$HOME/man/" or "$HOME/man:" results in the same.
Am I missing some
Hello,
As asked by Stuart, here are our exchanges regarding a problem I encountered
with isakmpd.
After applying the patch, I'm here to report my progress. I applied the patch
by hand on a stable 5.6 tree and didn't encountered any issue merging it.
In my first try, the VPN didnt went up. I was
On 2015-02-11, Hugo Osvaldo Barrera wrote:
> Can
> someone else confirm postgres9.4 work fine on the latest -snapshot? (the
> confirmation would be helpful to reafirm that it's not an issue with some
> dependency or library).
Works fine on my bacula box, running 9.4.1 (and previously 9.4.0) on am
On 2015-02-12, Jan Stary wrote:
> Would it be better if apm -l said the battery is
> (14.75 / 48.84) full now?
No, because then you wouldn't know when it had finished charging.
> My question is: what exactly makes 14.75 the last "full" capacity?
> How is that determined? Does the code for hw.sensors somehow observe
> the AC is connected, but it's not getting charged
> for the last $N minutes, so this must be the full capacity
> or is this just what the battery tells us vi
current/amd64 on a Thinkpad T400 (dmesg below).
The battery gets used, as batteries do.
With AC connected:
$ sysctl hw.sensors.acpibat0
hw.sensors.acpibat0.volt0=11.10 VDC (voltage)
hw.sensors.acpibat0.volt1=12.37 VDC (current voltage)
hw.sensors.acpibat0.power0=0.00 W (rate)
hw.sensors.acpibat0.
25 matches
Mail list logo
