A while back, Jon Strickland wrote a Cool Solutions article on how to enable RSS feed updates to notify you via your instant messenger client.
If you have an RSS feed, such as a blog or podcast, that you regularly monitor for changes, this is kind of a cool tip to check out.
Okay, time to finish off the “How to Update Banshee” posts. The Mighty Aaron Bockover has put up a repository for SLED10 and another for openSUSE 10.2 (openSUSE 10.2 is still being developed).
- If you followed my previous steps on buidling banshee from source, you have to uninstall all the packages before adding these. This is as easy as using “sudo make uninstall ” on each of the source folders from which you previously did the install, but going in reverse order. (If you did not save the source install folders, then you have a bigger problem–same as a couple of my systems–that I have yet to work out how to fix.)
- Remember that on SLED10 this is not officially supported by Novell, so this is not for production deployments.
1. Add the Banshee Update Repository to your Update Lists
- Start YaST2, and open the “Installation Source” tool
- Add a new HTTP installation source
- In “Server Name,” enter “dist.banshee-project.org”
- In “Directory on Server” enter “SLED-10/”
- Click OK
- Import the crypto certificate when presented
- Click Finish to close and save the added repository
(click the thumbnail at right to see interfaces)
2. Select the Banshee packages to Install/Update
- Start YaST2, and open the “Software Management” tool
- Select the following packages to Install or Update
(click the thumbnail at right to see interfaces)
- Main menu often locks up after installing the packages.
- Banshee start up does not complete on the first attempt.
- If you did my previous method for compiling banshee from source, Banshee may crash on each subsequent starts.
- Others? Please comment below.
This kind of thing doesn’t happen (to me) very often, so I figured I’d write about it here, before it fades away as a distant memory. I flew back to the UK on Monday, arrived Tuesday, and headed into the City of London for some customer visits. It was awesome to back in London, I haven’t really spent any time there since the daily commute into the Docklands almost 20 years ago. And woah, how Docklands has changed… what was once the home of “Eastenders” is now a stainless steel metroplex, with 30th floor wine bars, underground shopping and buildings intersecting light railway and tube lines. Approximately 23 hours after arriving in Heathrow, I was headed back to Utah. The only issue was a lack of laptop power on the airplane, and generally in airports, where I met John Mad Dog Hall when sharing a power outlet in order to get a boost before boarding one flight. He was running SuSE 10.1 on his laptop. And my Thinkpad T42p runs about 4 hours when playing with SLES10, Xen, LinuxHA (single-node cluster), and the Python WBEM client bindings to the DMTF CIM profiles for virtualization.
Just a reminder to you all about next year’s timezone changes. This affects anyone that’s in the US, does business with the US, travels to the US, has heard of the US – well, you get the picture. Daylight Savings Time (DST) is going to be starting 3 weeks earlier and ending a week later in most US and Canadian timezones next year, so you all need to take steps to make sure that you have an easy transition.Dean Lythgoe and 2 members of his team Kent Sievers and Craig Johnson have been working hard to create an advisory for all GroupWise customers, however, it contains information relevent to everyone. NTS has converted the advisory into a TID and you can read it here.
In short, make sure all your timezone defintions are correct on servers, workstations and in GroupWise and install the WebAccess updates that will be following soon. Don’t look right now, because we didn’t release them yet, but we should be releasing a public beta of GW7 SP2 and a GroupWise 6.5 update, probably next week. At least that’s the current plan unless someting-very-bad happens.
The WebAccess fix is going to contain two changes. The first is an update to hard coded timezones (in fact, it’s the removal of hard coded timezones and using the ones in the domain instead), and the second is a timezone detection routine that will update WebAccess sessions to use the timezone of the workstation that users are logging in from.
I need to check on GWIA as anecdotal evidence suggests that it also contains hardcoded timezone information that will break iCal appointments – so I’ll post an update here later.
 Yes, you do need a new GWIA too. This will be fixed in the 7.x codebase only as iCal wasn’t supported in 6.5. Only affects iCal appointments.
You should make your updates shortly after November 5 this year. We cannot stress enough the importance of your being on top of this to ensure next year’s transition is a smooth and as pain free as possible.
And in the words of a great Alabama native “That’s all I have to say about that”.
Yep, still in Alabama, learning some of the lingo. Still stuffing my face too – the other night I ordered a carpaccio starter, which I used to love in Holland but you can’t get in Utah. Well, should have known better than to order a starter when dining alone in the US because a plate at least 2 foot long (60cm in new money) and 9 inches wide (23cm) and covered end to end in meat arrived. That has definitely fixed my carpaccio craving for a while 🙂
Back to business, we released a new version of the Novell GroupWise 7 Gateway for Microsoft Exchange. Jeez, that’s a real mouthful of a name. Anyway, after we shipped the last version we discovered an issue with the gateway processing any HTML mail over 4kb.
It’s available here. It does not contain the new improved busy search that I mentioned previously, that’s still to come. It contains another fix for when you are using /blockdoms (which can’t be very many of you, otherwise you would have been crashing) and, my personal favourite, a fix for long log lines so that we no longer display a blank line.
Aaron Schwartz of JPMorgan put out a research note on Novell following yesterday’s Oracle announcement regarding support for Red Hat Linux. It makes a couple of interesting points. One is that “Novell’s Open Platform segment is less than 10% of aggregate revenue and stands to benefit more from broader enterprise Linux adoption (a goal of …
Novell SVP John Dragoon has put up a post on his blog with his take on today’s Oracle announcement regarding support for Red Hat. Worth a read.
If you are using ZENworks and Citrix within your environment, then you need to know about this. If you already know about this, then please proceed to the next post.
David Shepherd is a Senior ZENworks Consultant who is part of Novell Consulting, based in the UK. He lives, eats, breaths, drinks, and smokes ZENworks and Citrix on a daily basis. Throw in a hearty dose of Novell Identity Manager, and you’ve got yourself a Dave Shepherd well balanced diet.
Dave has put together a very descriptive document on how to integrate your ZENworks environment with your Citrix environment… you can find what’s available here. That being said, you will be happy to know that Dave is currently working on an updated version of this document/subject, which covers the latest and greatest versions of ZENworks and Citrix, along with some other cool content which I’m sure you will find detailed and useful.
Take a closer look… and you can be sure that we will update you when the new version of the document is available. Right here… on Cool Blogs!!
One of my colleagues (EZS) and I have been tossing around the idea of writing a new book covering ZENworks solutions design, architecture, best practices, ITIL, etc. etc. etc. A book that covers ZENworks stuff prior to administration, which is being well covered by Mr. Ron Tanner.
I’d like to hear back from you regarding topics that you think MUST be covered in the book… we’ll keep you up to date on progress as well.
Post your comments here… or email me at firstname.lastname@example.org.
Here’s a short policy smaple from Jeff Johnson that helps you automatically send an e-mail when a transaction is unsuccessful.