Hello, All;
I've added a property to CWM config to hide the window in the top
left corner of the screen while moving or resizeing a window.
This is my first patch, so feel free to yell at me.
Ben Raskin
diff --git app/cwm/calmwm.h app/cwm/calmwm.h
index a0aeafa8f..3904eeddf 100644
--
Added a window property show config option when resizing or
moving windows at top left corner of window being moved. Defaults to
showing property.
This is my first patch, free to yell at me if I did something wrong.
Ben Raskin
---
app/cwm/calmwm.h | 1 +
app/cwm/conf.c | 1 +
app/cwm
I've seen a few threads discussing OpenBSD on IBM Power Systems.
http://openbsd-archive.7691.n7.nabble.com/What-about-the-IBM-POWER7-and-POWER8-platforms-did-anyone-ever-think-about-porting-these-to-OpenBSD-td290583.html
Does anyone have an update/status report on the progress?
Regards
On Mon, Nov 12, 2018 at 06:46:26PM -0200, Martin Pieuchot wrote:
> On 11/11/18(Sun) 13:10, Ben Pye wrote:
> > Hey all,
> >
> > In my quest for better OpenBSD support on my Chromebook 13 I have found
> > that sdmmc(4)'s current strategy for suspend/resume onl
On Mon, Nov 12, 2018 at 06:50:27PM -0200, Martin Pieuchot wrote:
> On 09/11/18(Fri) 16:25, Ben Pye wrote:
> > On Thu, Nov 08, 2018 at 11:25:37PM -0600, joshua stein wrote:
> > > On Fri, 09 Nov 2018 at 03:30:07 +, b...@curlybracket.co.uk wrote:
> > > > Hi all,
>
On Sat, Nov 10, 2018 at 03:45:41PM +, Ben Pye wrote:
> On Sat, Nov 10, 2018 at 06:30:37AM +0000, Ben Pye wrote:
> > On Wed, Nov 07, 2018 at 05:33:13PM +0100, Mark Kettenis wrote:
> > > > From: Ben Pye
> > > > Content-Type: text/plain; charset="utf-8"
mmc_mem_mmc_init fails.
In it's current state this patch almost certainly breaks the
suspend/resume behaviour for non-removable devices, this should be
easily resolved once we can determine which sdmmc(4) devices are
removable.
Ben.
Index: sys/dev/sdmmc/sdhc.c
===
On Sat, Nov 10, 2018 at 06:30:37AM +, Ben Pye wrote:
> On Wed, Nov 07, 2018 at 05:33:13PM +0100, Mark Kettenis wrote:
> > > From: Ben Pye
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > I have been attempting to run OpenBSD on my H
On Wed, Nov 07, 2018 at 05:33:13PM +0100, Mark Kettenis wrote:
> > From: Ben Pye
> > Content-Type: text/plain; charset="utf-8"
> >
> > I have been attempting to run OpenBSD on my HP Chromebook 13, it's a
> > Skylake device with eMMC storage. Prev
27;t find a specific list of devices using this
protocol however some searching indicates that there are certainly more
than just the "ELAN" device present on my laptop. I unfortunately do
not have any other hardware with an Elantech trackpad so I can't really
see if this will w
c and the device gets stuck in sleep.
Thanks,
Ben.
Index: sys/arch/amd64/conf/GENERIC
===
RCS file: /cvs/src/sys/arch/amd64/conf/GENERIC,v
retrieving revision 1.464
diff -u -p -r1.464 GENERIC
--- sys/arch/amd64/conf/GENERIC 26 Oct 2018
sdhc such that it only sets the voltage if the request is
for a different level, this is the behaviour FreeBSD has.
Ben.
Index: sys/dev/sdmmc/sdhc.c
===
RCS file: /cvs/src/sys/dev/sdmmc/sdhc.c,v
retrieving revision 1.61
diff -u -p
Hi tech@,
I wasn't able to execute "zzz" (lower case) from the exec menu in cwm.
It
skipped over it when ordering the search results because "ZZZ" (upper
case) was already there.
This is my first patch, so please let me know if anything else is
needed.
Thanks,
Ben
This fixes a typo in the imsg example.
Index: lib/libutil/imsg_init.3
===
RCS file: /repo/OpenBSD/src/lib/libutil/imsg_init.3,v
retrieving revision 1.12
diff -u -p -u -r1.12 imsg_init.3
--- lib/libutil/imsg_init.3 11 Jun 2015 19
This patch adds any windows that are completely obscured by other
windows to the menu of currently hidden windows. I've found this very
useful. When I lose track of a window it doesn't matter to me whether
I intentionally hid it or it just became obscured, I just want to
bring it back easily with
I agree that one probably never gets a short write there in practice,
but if there is going to be a loop, it may as well be correct.
On Sat, Apr 26, 2014 at 10:52:50PM +0200, Ingo Schwarze wrote:
> Hi,
>
> On Tue, Apr 22, 2014 at 01:29:03AM +, Ben Cornett wrote:
>
> > The
Anybody have time to look at this?
On Tue, Apr 22, 2014 at 01:29:03AM +, Ben Cornett wrote:
> The following corrects the termination condition on the write
> loop in copyfile.
>
> Index: usr.sbin/vipw/vipw.c
> ===
The following corrects the termination condition on the write
loop in copyfile.
Index: usr.sbin/vipw/vipw.c
===
RCS file: /cvsroot/OpenBSD/src/usr.sbin/vipw/vipw.c,v
retrieving revision 1.16
diff -u -p -r1.16 vipw.c
--- usr.sbin/vipw/
Clarify the return value of getenv.
Index: lib/libc/stdlib/getenv.3
===
RCS file: /cvsroot/OpenBSD/src/lib/libc/stdlib/getenv.3,v
retrieving revision 1.19
diff -u -p -r1.19 getenv.3
--- lib/libc/stdlib/getenv.35 Jun 2013 03:39:23
I couldn't get the pppoe server to work on -current, rebuilt -current
yesterday and it now works - user error.
The following works in all the combinations 5.0 client/server userland
and with -current client/server and with -current pppoe(4).
-- ben
Index: cli
55.255.255 \
pppoedev em1 authproto pap authname user1 authkey secret123
and subsequently:
# ifconfig em1 mtu 1508 up
# ifconfig pppoe0 down
# ifconfig pppoe0 mtu 1500 up
with both:
server# pppoe -p pppoes1 -i em1 -s
and
server# pppoe -p pppoes2 -i e
Resend with unified diffs, sorry...
On 28 March 2011 20:11, Ben Gould wrote:
> Hi,
>
> A bug fix, performance improvement and a new feature for pppoe(8); and
> a performance improvement for ppp(8).
>
> pppoe(8):
>
> - Under load my low power atom-based router kept hitt
I probably wouldn't have needed to rewrite the
select() calls as kqueue()/kevent() if I had a faster computer acting
as a router. pppoe(4) seems to cause panics and wasn't setting up
IPv6 properly for me - sorry I've not investigated that further.
Diffs and dmesg follow.
-- ben
6k. But that if
there is memory pressure a reduction could be made. And it seems that most
operating systems are defaulting more around those numbers now days. So it
may make sense to instead look at some kind of slow connection sysctl with 0
for 8k window size, 64k max, 1 for 32k window size, 256k max, 2 for 64k window
size, 512k max. On a 56k modem even 8k window size can lead to massive
congestion though.
Ben.
On Fri, Dec 03, 2010 at 01:12:57PM +0100, Claudio Jeker wrote:
> On Fri, Dec 03, 2010 at 11:07:00PM +1300, Ben Aitchison wrote:
> > On Wed, Dec 01, 2010 at 10:39:20PM -0500, Ted Unangst wrote:
> > > yeah I found bumping to 64k made a big difference too, but for my
> > >
the data quick enough
causing issues?
If I set a static buffer at 49152, I get the same speeds as my (raised) default.
But if I use squid I get something more comparable to the speeds I get when I
raise buffer to 262144. (which isn't 5 times as fast fwiw)
So I'm assuming that some applications are not increasing the window size for
some reason or other;
Ben
ize in an
application - like squid, and relayd both support built in hard coding of
socket buffer size.
My current pet peeve is that if you bounce a connection that came in with
timestamps turned off, then you're initiating another connection with
timestamps on then you can end up with one 1
27 matches
Mail list logo
