Custom Query (1145 matches)

Reported by wdc, 16 years ago.

When you boot from older Intrepid media, you see an spew of kernel oops messages. The apparent work-around for this is to power cycle the machine.

A one-line change to print the error message only once is incorporated into the Intrepid update kernel, so this symptom only affects systems lacking the update kernel.

The warning is reporting a fault in the HPET clock which *IS* real. It takes forever for the system to boot up, and logging in takes rather long. The work around is to boot with the option acpi=off.

When you boot Jaunty, even from media as recent as 3/24, you get a blank screen unless you use the boot option acpi=off.

We need to find out where the fault lies and get it fixed.

Reported by wdc, 15 years ago.

If gnucash is started with the "Update Search Path" option, a seemingly benign default, creates a .gconf.path which thereafter forces Athena 10 to look at Athena 9 gconf defaults and suddenly your screen is a broken version of Athena 9 instead of the new Ubuntu setup.

Supplementary documentation on this issue:

 http://svn.gnucash.org/docs/help/first-time.html

 http://svn.gnucash.org/trac/browser/gnucash/trunk/src/gnome-utils/druid-gconf-setup.c#L90

removing .gconf.path seems unbreaks the gconf setup, and gnucash runs just fine without that file present,

The problem is that we can't seem to figure out how gnucash got it into its head that making that setup was necessary.

Let's see if we can get an initial gnucash startup to fail again like this and understand WHY it did this.

The two commands:

rm -rf ~/gnucash

gconftool-2 --recursive-unset /apps/gnucash

clears out all the identifiable gnucash state, but does NOT provoke it into a setup dialog that asks if the Gnome Path can be set.

Reported by wdc, 15 years ago.

Alexp has done the work of figuring out how to get TSM 5.4 working under Intrepid (including the dsmj GUI by utilizing the sun-java-6 JRE.)

Temporary documentation on getting this to work is pointed to by Hermes at:  https://web.mit.edu/sgi-desktop1/tsmdoc/article.html

There are several opportunities for improvement here:

1. Put the documentation in a more "real" place.
2. Refine the package to be a bona fide .deb instead of an alien.

IBM is coming out with a new version of TSM and this represents an opportunity to lobby for some important improvements:

1, Get rid of use of ksh since bash is canon nowadays, and the ksh EULA is really nasty.

2. Get TSM fully functional on the platform's NATIVE java runtime environment (preferably OpenJava?-6), rather than requiring TSM users to to go to www.sun.com, download a jre, click on a messy EULA, and then fiddle with the PATH.
3. Embrace Ubuntu as a supported platform.
4. Provide a simple installer akin to what is on offer for Windows or Mac.
5. Eliminate the need to hand-create the dsm.sys and dsm.opt files. (The installer should offer a gui setup for those.)
6. Create sensible interfaces to upstart that are appropriately installed by the installer.
7. Provide a "dry run" option that would help people see what files would or would not be backed up with a particular command or scheduled run.
8. Oh yes, I almost forgot, The TSM command line program should

use that ioctl to learn with the erase character is rather than hard coding the delete key. The erase character should be the upstream default, not requiring hand-tooling to specially fix for TSM.