More details here:
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg15620.html

zpoolreplace [-f] pool old_device [new_device] Replaces old_device with new_device. This is equivalent to attach- ing new_device, waiting for it to resilver, and then detaching old_device.

Let's face it: I am a lazy sysadmin ;-)

zpool replace is only needed for raidz vdevs.

Well, I though about writing a script for automagically filling-in the SVG document but I saw a few issues in my case and I don't think it worth the time (can be an amusing exam subject for students anyway):

1. As you mentioned, there are some numbers I don't want to have as fast call keys (e.g. *1, 123);
2. Another point is that the log only has the numbers, not the caller-id (i.e. real name) and in my LDAP directory, a single telephone-number can belong to multiple persons (I am considering to register places in addition to people to circumvent this limitation but I am not sure that this would really help making my life easier anyway). In such a situation, I can't rely on the directory information to retrieve the label corresponding to the number, and I have to pick a custom name myself;
3. Some names in the LDAP directory are a bit too long and required to be shortened to fit in;
4. A last point is grouping: I didn't want to order the numbers by how often I use them, but rather by the category they belong to (e.g. family, friends).

Taking all these rules into account would have required some non-trivial development, and as I don't plan to change these numbers every once a while, I stuck to filling-in the sheet myself.

However, in a company context, auto-filling-in the template definitively makes sense. In this case, using the same source to generate both the filled-in template (using XSLT) and the provisioning configuration files would make the fast call keys update for internal calls as easy as changing the sheet and rebooting the telephone!

Happy end of year season!

Merry Christmas!

Can you clarify the statement As of August 1st 2011, the freebsd-texlive projects distributes ports for using TeXLive 2011 from the FreeBSD ports tree

The FreeBSD-TeXLive project aims at providing TeXLive as ports for the FreeBSD operating system. This effort was started in late 2008 (texlive-2008) and is regularly updated to track the project upstream (currently texlive-2011). When a new TeXLive version is available, I try to post a note about the FreeBSD-TeXLive ports being updated to advertise a bit this project.

While I am a FreeBSD ports committer, TeXLive is not available through the FreeBSD ports collection: when the project was started, some other efforts where already engaged, but not yet public. Since I had basically no news since that, I am considering sharpening the FreeBSD-TeXLive ports to eventually bring them to the official tree: the teTeX maintainer has stopped the project more than 5 years ago, I think we have to switch!

This will require extensive work to update existing ports in the tree which depend on teTeX to make them use TeXLive instead (~150 ports).

In the meantime, you have to use portshaker(8) to merge the FreeBSD-TeXLive ports into the FreeBSD tree, and any port that depend on teTeX on your system will require a closer look to avoid installing conflicting packages.

Regards,
Romain

I have successfully installed 9.0-BETA 2 and have looked in /usr/ports/print/texlive-*, but it does not exist in native FreeBSD ports. Can you clarify the statement As of August 1st 2011, the freebsd-texlive projects distributes ports for using TeXLive 2011 from the FreeBSD ports tree on page http://code.google.com/p/freebsd-texlive/?

Due to many packages on FreeBSD depending on TeX mainly teTeX, I successfully removed the TeXLive 2010 install from my FreeBSD 8.2 amd64 box. I am using native teTeX on 2 of my 3 FreeBSD boxes. I don't see any TeXLive packages in native FreeBSD ports. I have also tried to install TeXLive through your advice in page using portshaker, but have not succeeded.

If I install TeXLive from TeXLive DVD 2011, I get working tex, but xdvi complain(s)(ed) about missing a file****.so and did not work correctly. I would like a tighter integration and would prefer if possible to get the full scheme installed and configure the ports that use teTeX to use TeXLive that you have made, but I have not succeeded.

Thank you for any pointers on this and if TeXLive is not in FreeBSD ports, despite your enormous contributions and dedications; there is sadly not much that we can do. Many users complain that TeXLive is a monster and that they prefer teTeX, but for me a full scheme is preferred as it has the majority of style files that one needs.

Regards,
Antonio

Unfortunately, there is no plan to merge the freebsd-texlive ports into the FreeBSD ports tree. I am considering pushing portshaker in the ports however to make it easier for people who want to use these ports, BSD# Ports, etc

BTW, the TeXLive and teTeX are not compatible. And no port for kile is available for using with TeXLive. Any contribution is welcome however :-)

Thanks!
Romain

I have recently installed FreeBSD 8.0. I had used FreeBSD 6 back a while and liked it but my disk died and I did not install it again. Now I installed on an AMD machine and installed kile and it pulled in tetex. teTeX is old and unmaintained, I applied your solution in google code, but the tex is still the old tex, how can I make sure that I have TeXLive installed?

I did not know many more things like cvsup/csup and I am learning a little bit more and currently updating to newer.

Thanks for your TeXLive work. When will it become part of FreeBSD? NetBSD has a port already? Is it like going to happen soon?

Regards,

Antonio

Maybe a base-dn error. Difficult to say without seeing the slapd.conf file. /var/log/debug.log may also contain useful details ;-)