Re: setxkbmap cannot completely set compose key

[Christian Weisgerber]

Xianwen Chen (陈贤文):

> I forgot to report maybe an important piece of information. I use scim
> to type in Chinese. I use the default xdm. Here is my .xsession:
> 
> export LC_CTYPE=en_US.UTF-8
> 
> export XMODIFIERS=@im=SCIM
> export GTK_IM_MODULE="scim"
> export QT_IM_MODULE="scim"
> scim -d

I suspect it works as intended for xterm.  The compose key handling
is a simple input method built into libX11.  You are swapping out
this default IM for the SCIM one.

This area of X11 seems to be virtually undocumented.
See XSetLocaleModifiers(3).

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: strongSwan cannot install IPsec policies on OpenBSD

[Peter Müller]

Hello openbsd-misc,

is anybody out there running strongSwan as an IPsec client for a net-to-net 
connection
on an OpenBSD machine?

If so, I would be very grateful to know which steps are necessary in order to 
successfully
route traffic through this n2n connection and what your ipsec.conf file (and 
other ones,
if necessary) looks like.

Sorry for bringing this up again, but I am out of ideas now and packaging 
strongSwan
for OpenBSD would not make sense if it could not be used properly. :-)

Thanks again for any advice on this.

Best regards,
Peter Müller

Server 5 SSD/best practice

[Oliver Marugg]

Hi

I’ve got a Supermicro 5028D desktop server with 5 identical SATA SSDs, 
there is no HBA no RAID card in. The purpose of the server is intended 
as web/smtp and some vmm vms (os plus /home & /var storage).
What are your suggestions or best practices configuring the device 
arrangement (eg. sofraid(4), bio(4),bioctl(4) OS 2x on 2x ssd raid1, 
data 3xssd raid5 or 1x single ssd for OS and 4x ssd raid5/10 or better 
ideas)?


many thanks
-oliver

Re: Cannot start conversation using talk

[ben]

>Appart from setting your address and host and domain names in /etc/hosts, do 
>you
>have a "lookup file bind" line in /etc/resolv.conf ? If you don't, it defaults
>to "lookup bind file", so it will query DNS first, and then look into
>/etc/hosts. There is a possibility this too can confuse talk.

Adding `lookup bind file` to resolv.conf solved the issue. Thank you,
Zeljko.

Ben Raskin.