"Dmitrij D. Czarkoff" writes:
> "Dmitrij D. Czarkoff" wrote:
>
>>Another thing that bothered me about video(1) from Xenocara is that it
>>does not maintain frame aspect ratio. The diff below adds panning to
>>maintain aspect ratio after resize.
>>
>>Comments? OKs?
>
> Ping.
ok jca@
--
jca |
"Dmitrij D. Czarkoff" wrote:
>Another thing that bothered me about video(1) from Xenocara is that it
>does not maintain frame aspect ratio. The diff below adds panning to
>maintain aspect ratio after resize.
>
>Comments? OKs?
Ping.
Index: video.c
==
This patch makes code more readable and removes empty fprintf() formats.
Index: io.c
===
RCS file: /cvs/src/bin/ed/io.c,v
retrieving revision 1.19
diff -u -p -r1.19 io.c
--- io.c22 Mar 2016 17:58:28 - 1.19
+++ io.c
On 2016/11/25 14:07, Leo Unglaub wrote:
> With harddrives getting bigger and bigger this will (sadly) become the
> default for a lot of future server and client installations.
Just because you have a large hard drive doesn't mean that you need GPT.
In disklabel, type 'b' to set the disk boundaries
Hi,
I would like to collect some reports on whether or not this change
helps with hot-(re)plugging SFP+ modules. In theory if a different
type of an SFP+ module is inserted we should re-initialize the PHY
and reset our media configuration. This should matter when a fiber
optics module is replaci
Hi,
I ran into problems with mtu sizes on interfaces (gif in my case) and
ospfd. mtu was not the same on both sites so adjacency could not be
formed. The mtu mismatch is also logged by ospfd.
Just changing the MTU with ifconfig is not enough in such a case. I did
not want to restart ospfd since t
On Fri, Nov 25, 2016 at 02:07:30PM +0100, Leo Unglaub wrote:
> Maybe it would be a good idea to put that directly in the installer. Because
> more and more people are going to have to use GPT and stuff in the future.
Yes it would be a good idea. I agree. But code doesn't write itself. ;)
Hey,
On 11/25/16 13:01, Stefan Sperling wrote:
cd /dev
sh MAKEDEV sd0
sh MAKEDEV sd1
dd if=/dev/urandom of=/dev/sd0c bs=1m
dd if=/dev/urandom of=/dev/sd1c bs=1m
fdisk -giy sd0
fdisk -giy sd1
This is wrong ^
Try again with:
fdisk -iy -g -b 960 sd0
fdisk -iy -g -b 960 sd1
yeah, this works
On Wed, Nov 23, 2016 at 09:10:44PM +0100, Stefan Fritsch wrote:
> On Wed, 23 Nov 2016, Rafael Zalamena wrote:
>
> > > Maybe something like this is enough already (untested):
> >
> > I tried your diff without Mike's if_vio diff and it doesn't panic anymore,
> > however it doesn't work.
> >
> > vi
On 25 November 2016 at 13:16, Martin Pieuchot wrote:
> Remove some leftovers of line disciplines that are no more, ok?
>
Sure.
Remove some leftovers of line disciplines that are no more, ok?
Index: bin/stty/print.c
===
RCS file: /cvs/src/bin/stty/print.c,v
retrieving revision 1.14
diff -u -p -r1.14 print.c
--- bin/stty/print.c23 Mar 2016 14:52:42 -
On Fri, Nov 25, 2016 at 12:45:27PM +0100, Leo Unglaub wrote:
> Hey,
>
> On 11/25/16 10:53, Stefan Sperling wrote:
> > It is certainly possible. I have a laptop booting UEFI with softraid
> > crypto and keydisk. Granted, that was installed over a year ago and
> > only upgraded since, no fresh insta
Hey,
On 11/25/16 10:53, Stefan Sperling wrote:
It is certainly possible. I have a laptop booting UEFI with softraid
crypto and keydisk. Granted, that was installed over a year ago and
only upgraded since, no fresh install.
How did you initialize the disk? The installer itself won't set up
softr
On Fri, Nov 25, 2016 at 12:50:25AM +0100, Leo Unglaub wrote:
> Hey,
> i am trying to install OpenBSD on a Raid1 created by softraid0. My drives
> are sd0 and sd1. The created raid1 is sd3. The install works fine until
> OpenBSD tryes to write the bootblocks. But it fails with the error message:
> "
14 matches
Mail list logo
