Tag: Solaris

TexLive on Solaris 10

TexLive is a very decent Latex implementation, however if you want to write DIN conformable letters using g-brief you might get an error message like that:

! LaTeX Error: Command \Telefon already defined.Or name \end... illegal, see p.192 of the manual.

See the LaTeX manual or LaTeX Companion for explanation.Type  H   for immediate help. ...

l.48 \newcommand\Telefon{\mvchr{84}}

This bug is in g-brief with newer versions of marvosym.sty. So all you have to do is edit line 48 of /texlive/texmf-dist/tex/marvosym.sty and uncomment it.

This bug might affect all unices, not only Solaris.

3 comments » | articles

Sun RAY with PS2 Keyboards

SUN Ray with PS2 keyboards
If you want to hook up a Sun Ray at home, you might want to use your favourite old PS2 keyboard attached via some USB connector. Depending on your keyboard layout you might be disappointed by the result, because it will be standard US. That’s because the PS2 keyboard isn’t designed for the Ray clients and won’t prompt back a valid layout to the server which will then assume a standard scenario.
There is a simple solution to this problem; in the file “/usr/openwin/etc/keytables/keytable.map” edit the entry

6      0       US6.kt

and rewrite it to your favourite layout(British English in this case)

6       0      UK6.kt

There is one drawback however; from this point on this is going to be the single standard fallback layout for all keyboards hooked via SUN Ray clients to your server which won’t report a valid layout themselves. So if you want to use different layouts on different clients you might want to check the xkb option in “/opt/SUNWut/bin/utxconfig”, which I haven’t done until now.

1 comment » | articles

Multiple IP addresses on one interface (Solaris)

Like we mentioned earlier we are in the middle of configuring a Fire 280R server for our needs. Yesterday we finally were able to patch some real Internet addresses on the NICs, as well as new local addresses, so now we finally are online^^
While configuring we figured that there are at least three potential needs to assign multiple IP addresses to a single interface.

1. To do a quick test where the configuration won’t have to survive a reboot
2. On an interface in a global zone
3. On an interface in a non-global zone

These are the solutions we used:


$ ifconfig abrX:Y plumb

while “abrX” is the abbreviation for an installed interface.
Now you can use the new interface abrX:Y as you want.

We needed it to have an an external(Internet) and an internal address. So we made an entry in /etc/hosts for the primary address in the old fashioned way(we do not yet use NWAM):    fire

while we put the other addresses in /etc/hostname.abrX:


where /24 implies: netmask ffffff00 broadcast

We wanted the interfaces to be visible from the global zone via a local address while being available from the Internet. Therefore we defined a local address as in 2 via /etc/hosts and /etc/hostname.abrX, but we also included the Internet address in the zone configuration:

$ zonecfg -z zone1
zonecfg:zone1> select net physical=abrX
zonecfg:zone1:net> set address=
zonecfg:zone1:net> end
zonecfg:zone1> commit
zonecfg:zone1> exit

We will now take a look at IP instances, because using them we can achieve to only have the non-global zones visible in the Internet, while the global zone is only vulnerable in the local subnet.

3 comments » | articles

« Previous Entries