First, thanks to the OpenIndiana people. It's just what we've all
been waiting for, and I now have it installed on my laptop at home, a
Toshiba Satellite Pro P300 (which is where I am just now), and my
workstation at work, a Sun Ultra 20 M2.
Two things have been biting me. On my (UK) laptop the keyboard layout
is all over the place.
bash-4.0$ lshal | fgrep input.x11
input.x11_driver = 'mouse' (string)
input.x11_options.XkbVariant = '' (string)
input.x11_options.XkbLayout = 'us' (string)
input.x11_options.XkbModel = 'sun_type6_usb' (string)
input.x11_options.mdriver = 'hotkey' (string)
input.x11_driver = 'kbd' (string)
input.x11_options.XkbRules = 'base' (string)
bash-4.0$
It means <>"\|~...@#£ are all moved around. I guess I can mess around with
configuration files, but how should this work automatically ?
Worse is the new NWAM functionality. On my laptop talking wireless it
almost worked, until I tried to set up a Home location when it decided
to replace nsswitch.conf with /etc/nodename (!). That didn't work so
well, and I certainly didn't enter that as an option.
My workstation was worse, though. It's configured with NIS + DNS and
NFS filestore. It took me a few iterations of fixing nsswitch.conf and
rebooting before I realised NWAM was replacing it with nsswitch.files.
Looking at the NWAM configuration it was referring to
/etc/svc/volatile/nwam/User/nsswitch.conf, which didn't exist. There
was a .../Legacy/... file which was my old copy, and copying that to
.../User/... (and to /etc/nsswitch.conf) got me halfway there. I think
the handling of nsswitch.conf is rather fragile for such a fundamental file.
Fixing that and running `sharectl -p nfsmapid_domain=... nfs' to match
what used to be in /etc/default/nfs has got me back working.
Anyway, I just need to sort out my keyboard mapping, and I'll be a happy
bunny.
Thanks for all your work.
Rob
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
