2009-01-13
OpenSolaris can do CIFS and save my day
The OpenSolaris OpenSolaris CIFS service is really cool and has just saved me from loosing all my digital pictures. I have a laptop with XP that holds all my digital pictures (tens of thousands) and it has started to give up. XP tends to do that over time. So, I realised that I have a desktop with OpenSolaris installed since way back. It has lots of disk so I just did a 'pkg image-update' and there I was with a machine capable of acting as the family workgroup data server via CIFS. Really cool. Google for OpenSolaris CIFS workgroup to learn more. Just a couple of commands and off you go...
2009-01-06
Koha is best with Latin1
So, I've spent like 7 full working days on trying to get Koha to work with UTF-8 for no good at all. I switched all configs to Latin1 and suddenly it works somewhat better. Here's how I did;
vim /etc/apache2/apache2.conf
-----------------------------
#AddCharset UTF-8 .utf8
#AddDefaultCharset UTF-8
AddDefaultCharset ISO-8859-1
AddCharset ISO-8859-1 .iso8859-1 .latin1
vim /etc/php5/apache2/php.ini
----------------------------
#default_charset = "UTF-8"
default_charset = "ISO-8859-1"
vim /etc/mysql/my.cnf
(pid-file = /var/run/mysqld/mysqld.pid)
---------------------
#[client]
#character_set_client=utf8
#[mysql]
#default-character-set=utf8
#[mysqld]
#init-connect = 'SET NAMES utf8'
#character-set-server=utf8
#collation-server=utf8_swedish_ci
[client]
default-character-set=latin1
#[php-cgi]
#default-character-set=latin1
[mysql]
default-character-set=latin1
#[mysqladmin]
#default-character-set=latin1
[mysqlcheck]
default-character-set=latin1
[mysqldump]
default-character-set=latin1
[mysqlimport]
default-character-set=latin1
[mysqld]
init-connect='SET NAMES latin1'
character-set-server = latin1
default-character-set = latin1
collation-server=utf8_swedish_ci
vim /etc/apache2/apache2.conf
-----------------------------
#AddCharset UTF-8 .utf8
#AddDefaultCharset UTF-8
AddDefaultCharset ISO-8859-1
AddCharset ISO-8859-1 .iso8859-1 .latin1
vim /etc/php5/apache2/php.ini
----------------------------
#default_charset = "UTF-8"
default_charset = "ISO-8859-1"
vim /etc/mysql/my.cnf
(pid-file = /var/run/mysqld/mysqld.pid)
---------------------
#[client]
#character_set_client=utf8
#[mysql]
#default-character-set=utf8
#[mysqld]
#init-connect = 'SET NAMES utf8'
#character-set-server=utf8
#collation-server=utf8_swedish_ci
[client]
default-character-set=latin1
#[php-cgi]
#default-character-set=latin1
[mysql]
default-character-set=latin1
#[mysqladmin]
#default-character-set=latin1
[mysqlcheck]
default-character-set=latin1
[mysqldump]
default-character-set=latin1
[mysqlimport]
default-character-set=latin1
[mysqld]
init-connect='SET NAMES latin1'
character-set-server = latin1
default-character-set = latin1
collation-server=utf8_swedish_ci
Koha and UTF-8
So, once again I took the fight with Koha to make it work with non ASCII characters. I set the the following variables for MySQL, Apache and PHP
However when I try to add an item it cuts of the text at the non ASCII char. Look at these pictures:
Looks good (and a good book too)
Now I import the search result:
See, the prominent writer JMG Le Clézio is imported as "Le Cl", text cut at the é.
I can't put my finger on where the error is but it feels like it's PHP that is bugging me...
Update1: I went into the System Preferences->Intranet and changed Template Encoding to UTF-8 ( from ISO 8859-1). Guess what happened? Now the text is still cut and the non ASCII character is shown like a �
This drives me nuts...
vim /etc/apache2/apache2.conf
AddCharset UTF-8 .utf8
AddDefaultCharset UTF-8
vim/etc/php5/apache2/php.ini
default_charset = "utf-8"
vim /etc/mysql/my.cnf
[client]
character_set_client=utf8
[mysql]
default-character-set=utf8
[mysqld]
init-connect = 'SET NAMES utf8'
character-set-server=utf8
collation-server=utf8_swedish_ci
/etc/rc3.d/S19mysql restart
mysql> SHOW VARIABLES LIKE 'character_set%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
8 rows in set (0.01 sec)
mysql> SHOW VARIABLES LIKE 'collation%';
+----------------------+-----------------+
| Variable_name | Value |
+----------------------+-----------------+
| collation_connection | utf8_general_ci |
| collation_database | utf8_swedish_ci |
| collation_server | utf8_swedish_ci |
+----------------------+-----------------+
3 rows in set (0.00 sec)
However when I try to add an item it cuts of the text at the non ASCII char. Look at these pictures:
Looks good (and a good book too)
Now I import the search result:
See, the prominent writer JMG Le Clézio is imported as "Le Cl", text cut at the é.
I can't put my finger on where the error is but it feels like it's PHP that is bugging me...
Update1: I went into the System Preferences->Intranet and changed Template Encoding to UTF-8 ( from ISO 8859-1). Guess what happened? Now the text is still cut and the non ASCII character is shown like a �
This drives me nuts...
2008-07-23
Install only in global zone
If you have several zones on your machine then you might not want to install all packages into all zones. User tools like StarOffice are mostly only needed in the global zone.
pkgadd -G
will do the trick.
Two ways a pkg can be installed in the global zone only.
a) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=true
b) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=false
# pkgadd was run with -G
Trolling though the installed pkginfo files will give you (a), but
not (b). What you're probably looking for is
/var/sadm/install/gz-only-packages. That's a private interface though.
For Blastwave packages one can set the environment variable ADMINFLAG=' -G'
(Looks however that this is also passed to pkgrm which bails out. Have to check this...)
Looks like PKGADDFLAGS=-G is another way. Will check....
pkgadd -G
will do the trick.
Two ways a pkg can be installed in the global zone only.
a) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=true
b) SUNW_PKG_ALLZONES=false
SUNW_PKG_THISZONE=false
# pkgadd was run with -G
Trolling though the installed pkginfo files will give you (a), but
not (b). What you're probably looking for is
/var/sadm/install/gz-only-packages. That's a private interface though.
For Blastwave packages one can set the environment variable ADMINFLAG=' -G'
(Looks however that this is also passed to pkgrm which bails out. Have to check this...)
Looks like PKGADDFLAGS=-G is another way. Will check....
2008-07-16
On command
Ever wanted quick access to manpages?
User Commands
Systems Administartion Commads
System Calls
Thank's goes to Doug and the docs.sun.com team.
User Commands
Systems Administartion Commads
System Calls
Thank's goes to Doug and the docs.sun.com team.
2008-07-13
General instructions on updating to the latest OpenSolaris development build
Corrected instructions from what was first announced. (UNMOUNT)
Enclosed below are revised instructions for using "pkg image-update" to
update to the latest OpenSolaris development builds via
http://pkg.opensolaris.org/
For more information on this command and the Image Packaging System
(IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual
pages and the following documents
Getting Started With the Image Packaging System
http://dlc.sun.com/osol/docs/content/IPS/ggcph.html
Upgrading and Managing Your Boot Environments
http://dlc.sun.com/osol/docs/content/IPS/snap3.html
General instructions for updating to the latest OpenSolaris development build
=============================================================================
1) Before using the "image-update" subcommand, it is recommended that
the latest available version of the IPS software be installed for your
current boot environment (BE)
$ BUILD=`uname -v | sed s/snv_//`
$ pfexec pkg refresh
$ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
$ pfexec pkg install entire@0.5.11-0.$BUILD
2) Verify the build of OpenSolaris in the current BE
$ echo $BUILD
3) If you are running build 93 or greater, you can use "image-update"
directly as follows
$ pfexec pkg image-update
At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.
4) If you are using a build prior to 93, it is recommended one apply
the update directly to an alternate BE in order to work-around
2387 libbe.so:beCopy() frees nvlist variables before using them
http://defect.opensolaris.org/bz/show_bug.cgi?id=2387
First, display the list of the existing BEs on the system
$ beadm list
BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris no no - 3.92G
opensolaris-1 yes yes - 17.06M
Next, choose the name of a new BE - if the most recent created BE is of
the form "opensolaris-" where is an integer, then a suitable
choice for the new BE is "opensolaris-". In the above example,
the new BE would be "opensolaris-2".
Finally, execute the following sequence of commands to create, mount
and update the new BE
$ pfexec beadm create opensolaris-
$ mkdir /tmp/mnt$$
$ pfexec beadm mount opensolaris- /tmp/mnt$$
$ pfexec pkg -R /tmp/mnt$$ image-update
5) If you are running build 86, the following step is required in order
to work-around
1979 libbe: be_activate needs to run installgrub
http://defect.opensolaris.org/bz/show_bug.cgi?id=1979
>>>>>>>>>> IMPORTANT <<<<<<<<<<
Due to changes in the GRUB boot system, one must manually update the
Master Boot Record (MBR) to include these latest changes. Failure to
follow these instructions when updating from 2008.05 (build 86) to a
later build will result in a system that does not boot by default and
instead the original BE must be manually selected.
Update the GRUB configuration on your ZFS boot device(s) using
$ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$
6) Unmount and activate the newly created BE
$ pfexec beadm unmount opensolaris-
$ pfexec beadm activate opensolaris-
At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.
Enclosed below are revised instructions for using "pkg image-update" to
update to the latest OpenSolaris development builds via
http://pkg.opensolaris.org/
For more information on this command and the Image Packaging System
(IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual
pages and the following documents
Getting Started With the Image Packaging System
http://dlc.sun.com/osol/docs/content/IPS/ggcph.html
Upgrading and Managing Your Boot Environments
http://dlc.sun.com/osol/docs/content/IPS/snap3.html
General instructions for updating to the latest OpenSolaris development build
=============================================================================
1) Before using the "image-update" subcommand, it is recommended that
the latest available version of the IPS software be installed for your
current boot environment (BE)
$ BUILD=`uname -v | sed s/snv_//`
$ pfexec pkg refresh
$ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
$ pfexec pkg install entire@0.5.11-0.$BUILD
2) Verify the build of OpenSolaris in the current BE
$ echo $BUILD
3) If you are running build 93 or greater, you can use "image-update"
directly as follows
$ pfexec pkg image-update
At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.
4) If you are using a build prior to 93, it is recommended one apply
the update directly to an alternate BE in order to work-around
2387 libbe.so:beCopy() frees nvlist variables before using them
http://defect.opensolaris.org/bz/show_bug.cgi?id=2387
First, display the list of the existing BEs on the system
$ beadm list
BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris no no - 3.92G
opensolaris-1 yes yes - 17.06M
Next, choose the name of a new BE - if the most recent created BE is of
the form "opensolaris-
choice for the new BE is "opensolaris-
the new BE would be "opensolaris-2".
Finally, execute the following sequence of commands to create, mount
and update the new BE
$ pfexec beadm create opensolaris-
$ mkdir /tmp/mnt$$
$ pfexec beadm mount opensolaris-
$ pfexec pkg -R /tmp/mnt$$ image-update
5) If you are running build 86, the following step is required in order
to work-around
1979 libbe: be_activate needs to run installgrub
http://defect.opensolaris.org/bz/show_bug.cgi?id=1979
>>>>>>>>>> IMPORTANT <<<<<<<<<<
Due to changes in the GRUB boot system, one must manually update the
Master Boot Record (MBR) to include these latest changes. Failure to
follow these instructions when updating from 2008.05 (build 86) to a
later build will result in a system that does not boot by default and
instead the original BE must be manually selected.
Update the GRUB configuration on your ZFS boot device(s) using
$ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$
6) Unmount and activate the newly created BE
$ pfexec beadm unmount opensolaris-
$ pfexec beadm activate opensolaris-
At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.
2008-07-12
Another interesting service
Drupal is something I have to look into.
Here's more about Drupal in OpenSolaris 2008.05
And also with NetBeans 6.1
Here's more about Drupal in OpenSolaris 2008.05
And also with NetBeans 6.1
2008-07-02
Laptop as demo for Sun Ray server
Another test I have to carry out. I better get a fresh dual core Intel, 4GB RAM, nvidia graphic laptop and Win2003 server to test this out and be able to do demos. Also I have to test SRSS 4 on OpenSolaris 2008.05/snv_91
2008-07-01
Shoot myself in the foot
I managed to shoot myself in the foot playing with OpenSolaris 2008.05 Image Packaging System. So now I started over. No data loss but embarrassing...
Anyway, that let me set up my system even better adding the knowledge I've gained during the last couple of weeks.
As this is early birds, there are some special steps to consider.
Boot up from the LiveCD and install with ZFS on one disk. It takes 15 minutes on a decent machine.
After the reboot log in as the user you created at install (not root), open a terminal and do like this.
$ pfexec pkg refresh --full
$ pfexec pkg install SUNWipkg@0.5.11-0.86
$ pfexec pkg refresh --full
$ pfexec pkg image-update
The image update takes 1-2 hours depending on network speed so be patient.
Don't forget to update GRUB (Needed just only the first time you update after a fresh install)
$ pfexec mount -F zfs rpool/ROOT/opensolaris-1 /mnt
$ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt
$ pfexec init 6
Now you have the most modern UNIX on your machine and you can start adding development tools or whatever you need.
$ pfexec pkg install openoffice
Anyway, that let me set up my system even better adding the knowledge I've gained during the last couple of weeks.
As this is early birds, there are some special steps to consider.
Boot up from the LiveCD and install with ZFS on one disk. It takes 15 minutes on a decent machine.
After the reboot log in as the user you created at install (not root), open a terminal and do like this.
$ pfexec pkg refresh --full
$ pfexec pkg install SUNWipkg@0.5.11-0.86
$ pfexec pkg refresh --full
$ pfexec pkg image-update
The image update takes 1-2 hours depending on network speed so be patient.
Don't forget to update GRUB (Needed just only the first time you update after a fresh install)
$ pfexec mount -F zfs rpool/ROOT/opensolaris-1 /mnt
$ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt
$ pfexec init 6
Now you have the most modern UNIX on your machine and you can start adding development tools or whatever you need.
$ pfexec pkg install openoffice
2008-06-25
Core dump?
This is an extreme amount of cores that Sun will dump on us and shows that they are really ahead of the game. This will make a brilliant server for virtualization.
IPS
Managed to make a fool of myself today mixing up blastwave.org with blastwave.network.com in a question on the opensolaris.org indiana forum. I'm although not convinced that blastwave.org is fully operational as IPS package repository for an updated OpenSolaris 2008.05 installation i.e. one upgraded to snv_91.
2008-04-25
OpenSolaris rules
There was another one of those "Blame OpenSolaris for all you can think about" articles on /. today http://tech.slashdot.org/article.pl?sid=08/04/24/1723226
I find it most amusing that the Linux kids never grow up enough to work with real UNIX. It's as if everything isn't exactly as in their favorite distro, it's bad. And then they blame OpenSolaris for their own shortcomings. And throw up on ZFS just because. Is it to much Jolt, or?
Ranting about that they cannot add whatever they want is so kiddish. Solaris is a state of the art UNIX system and one of the most stable environment around. There must be control and if that's to hard to understand, stay with the toys.
I find it most amusing that the Linux kids never grow up enough to work with real UNIX. It's as if everything isn't exactly as in their favorite distro, it's bad. And then they blame OpenSolaris for their own shortcomings. And throw up on ZFS just because. Is it to much Jolt, or?
Ranting about that they cannot add whatever they want is so kiddish. Solaris is a state of the art UNIX system and one of the most stable environment around. There must be control and if that's to hard to understand, stay with the toys.
2008-03-08
VirtualBox
The acquisition of German based Innotek with its VirtualBox was a nice move by Sun. I'm now downloading it for both OpenSolaris and Windows XP to test run OpenSolaris on XP and XP on OpenSolaris (plus some Ubuntu I think). Will be interesting...
2008-01-20
Symptomatic???
http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers
OpenOffice.org Wiki has a problem
Sorry! This site is experiencing technical difficulties.
Try waiting a few minutes and reloading.
(Can't contact the database server: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (146) (localhost))
Nice move
CEO Jonathan Schwartz of Sun Microsystems has announced that they will buy the Swedish software company MySQL AB, http://blogs.sun.com/jonathan/date/20080116.
I think that is one of the best moves Sun has done in a long time. Much better than changing SUNW to JAVA as stock ticker or buying STK.
I think that is one of the best moves Sun has done in a long time. Much better than changing SUNW to JAVA as stock ticker or buying STK.
Subscribe to:
Posts (Atom)
