2007-07-25

High Fructose Corn Syrup (HFCS)

[this item cross-posted to earth_food at http://blogs.earthside.org/earth_food/2007/07/high-fructose-corn-syrup-hfcs.html]

We've been hearing that "high fructose corn syrup (HFCS) is not good for you" for a couple years now, but up until now it has just been something to avoid if possible (i.e. choose the brands that don't have it in the ingredient list if and when an alternative is available, pass up certain "SALE" items because they contain it, etc), but - at least up until this point, no evidence concerning HFCS has been presented (to me), and no critical warnings have been raised about its use in human food products.

Today while moderating a discussion at slashdot.org entitled PubPat Kills Four Key Monsanto Patents, I ran across a post (#19982005 by an "anonymous" author) which - while substantially directed at the issue of genetically modified (GM) crops, mentions some of the reputed [according to the anonymous author] problems with HFCS and includes some [supporting] internet links.

We've had HFCS on a sort of "probationary" status for some time since it's lack of usefulness for human consumption was first brought to our attention a few years ago.

At the present time, HFCS seems destined for infamy on that list I carry around in my head of "poisonous items which are disguised as food and to which the U.S. FDA turns a blind eye." Items which are already on that list include, but are not limited to:

  • aspartame
  • fluoride

The [anonymous] author of the /. post quotes from a source at http://ezinearticles.com/?The-Dangers-of-High-Fructose-Corn-Syrup&id=28535, which quote is reproduced again, here, in part:

When high fructose corn syrup breaks down in the intestine, we once again find near equal amounts of glucose and fructose entering the bloodstream. As covered in recent newsletters, the fructose short-circuits the glycolytic pathway for glucose. This leads to all the problems associated with sucrose. In addition, HFCS seems to be generating a few of its own problems, epidemic obesity being one of them. Fructose does not stimulate insulin production and also fails to increase "leptin" production, a hormone produced by the body's fat cells. Both of these act to turn off the appetite and control body weight. Also, fructose does not suppress ghrelin, a hormone that works to increase hunger. This interesting work is being done by Peter Havel at UC Davis.

Some of the problems associated with high fructose corn syrup:

  • Increased LDL's (the bad lipoprotein) leading to increased risk of heart disease.
  • Altered Magnesium balance leading to increased osteoporosis.
  • Increased risk of Adult Onset Diabetes Mellitus.
  • Fructose has no enzymes or vitamins thus robbing the body ofprecious micro-nutrients.
  • Fructose interacts with birth control pills and can elevate insulin levels in women on the pill.
  • Accelerated aging.

2007-07-21

FEMA Continues to Contribute to Katrina Death Toll

Democracy Now! is reporting that FEMA suppressed warnings of toxic gases [formaldehyde] in trailers issued for the use of persons evacuated from the destruction wreaked by Hurricane Katrina. From the Headlines page for 20 July 2007:

FEMA Suppressed Warnings on Toxic Gas in Evacuee Trailers
[…] documents show top Federal Emergency Management Agency officials have suppressed internal warnings about dangerous levels of toxic chemicals in trailers inhabited by Hurricane Katrina evacuees […] FEMA field workers warned the evacuees were living amidst levels of potentially cancerous formaldehyde gas […] seventy-five times the recommended maximum […] Hundreds have complained of health effects […] emails show FEMA officials were only concerned with avoiding any legal liability … a FEMA official wrote [that] agency lawyers had advised against carrying out tests because doing so: “would imply FEMA’s ownership of this issue.” […] FEMA lawyer Patrick Preston wrote: “Do not initiate any testing until we give the OK … Once you get results […] the clock is running on our duty to respond to them.” Eleven days later, an evacuee who had complained about the chemicals was found dead in his trailer. […] FEMA attorneys rejected calls for an independent investigation into his death […].

It is interesting to note that as of 08:21 EST Saturday 21 July 2007 [the time of this writing] the GSA auction site at http://gsaauctions.gov/gsaauctions/gsaauctions/ where these trailers are being auctioned is unavailable, returning an HTTP 503 "503 Retry request – Service will be available shortly. Please retry request" error for repeated retries.

This sort of incident brings forcefully to mind the actions of the European settlers to North America in giving blankets contaminated with smallpox to the native tribes residing in the territory upon which the Europeans wished to settle. I.E. There have been repeated allegations amongst the Katrina survivor community to the effect that the Federal government planned to use the disastrous events surrounding the hurricane to depopulate New Orleans in order that the city might be turned over to corporate interests.

The story in the Washington Post titled FEMA Announces Trailer Air Testing Plans, also dated 20 July, mentions several other FEMA-trailer-related deaths and lawsuits which have been filed.

A point which is mentioned in the Washington post article is that at least one of the lawsuits which has been filed, and which is attempting to gain class action status, is against the trailer manufacturer.

  1. Why is/was FEMA concerned with liability when in fact the manufacturers who produced trailers purchased by FEMA are the ones who ultimately bear liability for their unsafe product?
  2. These trailers purchased and distributed by FEMA are brand­name, commercially available "Recreational Vehicles" (RVs) – if the formaldehyde levels in them are sufficient to kill the occupants – even if the occupants killed are "infirm" or suffer from respiratory problems – how is it that the manufactures are allowed to sell these deathtraps to the public?
  3. If private individuals purchase these trailers and resell them, will they be responsible for "cleanup" of the toxic materials in them, and if so, what sort of toxic materials handling and disposal certifications will be required of them?

[note that the GSA auction site is back online as of 09:24 EST today, 21 July 2007 - no explanation of the outage provided on the GSA page]

2007-07-19

Additional info about Konqueror, Blogger Dashboard, and Spell Checking

Apparenlty the prooblem with Konqueror dying trying to load the Blogger.com Dashboard was temporary. This post is made using Konqueror 3.5.2 (KDE 3.5.2). It appears that the problem may have had somewhat to do with the Spell Checker problems I was trying to post about earlier (at the time the Konqueor crash occurred.

The problem then was that Konqueror as configured by default under Knoppix 5.0.1 was still using the German language dictionary for spell-checking, even though I had changed the KDE language preference to US English (US-EN) using the KDE Kicker panel [I.E. "toolbar"] widget.

I have since restarted KDE (due to some problems that seemed to have been caused by my moving the system /tmp directory to an internal drive partition while KDE was still running) and Konqueror starts up and runs and has not [yet] crashed on the Blogger Dashboard interface.

The earlier crash which killed Konqueror for the duration of that KDE session occurred after the problems with the spell checker manifested, and after I clicked the Save Now button to save the post. The Save Now button did not "depress" at that time, and no draft of the message was saved. Immediately after the save operation failed is when I clicked the Dashboard link, which is what caused Konqueror to crash.

Note that at this time, the spell checker does not seem to be working at all in Konqueror (the Auto Spell Check option is checked, and the Check Spelling context menu command does nothing), and that

  1. There is no "typeahead" pattern matching in the tags field of the blogger.com Posting interface as there is with Firefox v2.x
  2. The layout of the blogger.com Posting interface in Konqueror is munged - there is a large whitespace block below the text entry area, between the bottom edge of the HTML textarea element and the the bottom edge of the boarder which encloses the HTML element. (above the Post Options link, the Labels (sic) [tags] entry field, Publish Post and Save Now buttons, etc.

erratta: KNOPPIX audio is working

This is to correct a statement I made previously in a post on this log [earth tech] about KNOPPIX and the audio capability on the HP Pavilion a220n.

The audio input does in fact work under the KNOPPIX 5.0.1 LiveCD release. I missed this because, while the audio output worked fine once the audio sub-system was enabled via the KDE Control Center | Sounds & Multimedia | Sound System control panel, the mic input levels were defaulting to zero, so no singal was being captured.

Links:

Additional problems with blogger.com

Another problem that has shown up recently with blogger.com recently is some strange behavior under Firefox v2.0.0.4 and v2.0.0.5 - specifically, the Posting interface, when certain buttons are clicked, does not behave as expected.

For instance, the "Link&qut; button [supposed to add an HTML anchor (A) element in the text box where the blog post is entered and/or edited:

When the link button is clicked, Firefox apparently initiates a "Drag and Drop" operation for the button image. The URL entry box pops up as expected, but the pointer cursor is changed to indicate that a drag/drop is in progress, and if the user clicks within the URL entry field on the popup, the URL of the button image [at blogger.com] is pasted into the URL entry field. If the user clicks outside the text entry field on the popup, the "drop" part of the drag/drop operation fails silently and text can be entered.

For some reason the drag operation does not provide the "NO" symbol cursor on screen areas which will not accept the dragged image.

This is almost certainly a Firefox issue, rather than Blogger issue, but it is possible that it is something funky w/ the Javascript Blogger uses. I have not examined the Javascript source or tried to replicate this error on other sites or with other browsers (although the same issue does exist with Iceweasel under Debian).

2007-07-18

Blogger.com Dashboard Crashes Konqueror

Well, the Dashboard page at blogger.com seems to have killed Konqueror web browser under KNOPPIX. Konqueror crashed first while I was trying to post about the spell-checker problems that exist in Konqueror under the KNOPPIX LiveCD distro - at that point I was logged in to blogger.com - then it crashed again when I re-ran Konqueror and tried to log in to the blogger.com dashboard. Both times it gave the DrKonqi crash-handler screen.

Now, after I created a persistent installation of Firefox 2.0.0.5 and ran it to make this post, I find (while trying to run Konqueror to get the version number to use in this post) that Konqueror won't run at all [from the toolbar button, at least - haven't tried any other approaches, yet]; it shows the bouncing "wait" cursor for about 15 or so seconds, then just dies silently.

This is Knoppix 5.0.x - I don't have the version number to-hand, but I may be able to post it later. I see that Knoppix 5.2 is released, so the problem may be solved by burning a new LiveCD. Note, however, that the version of K3B that shipped with this version of KNOPPIX does not work - or at least, it doesn't work on this computer, so the burning of a new CD is problematic, right now.

2007-07-16

Bash du+sort Script

This is a one-liner that shows something about why grep has behaved so strangely in the past when we've tried to feed it regular expressions as the pattern to match:

  du -h | grep  "^[1-9]\+\.[0-9]\+[M]" | sort 

The trick here was to add the backslashes ('\') in front of the plus signs ('+'). apparenlty grep interprets the '+' literally if it is not escaped.

Note A: the Debian-blows-goats version of grep is not built with support for Perl regular expressions (bug #15051), which figures, since the Debian-POS developers only seem to know Python.

Note B: it apparenlty makes no difference to [this version] grep if the quote delimiters used in the above command are single- or double-quotes [this is counter-intuitive, since use of single quotes typically means no escape characters are needed], but the quotes must be there for the command to work - leaving them out causes the command to emit no output.

Solution to Debian's Problem with 'mount /dev/sda1'

There is a problem - as mentioned previously - with the default Debian-blows-goats install. For whatever reason, the system refuses to mount a USB mass-storage device when it is connected - that is, the Debian-POS system neither automounts the new storage device, nor will it allow either root or any loggeg-in use to mount it, despite the appropriate entries in /etc/fstab and the expected messges in /var/log/messges.

The forum thread /dev/sda1 missing [now closed] at LinuxForums describes the problem, some attempts at solutions, and some "workarounds" (see our post Found a workaround, maybe...) in detail, but the information we're posting here is not there [or if it is, it's in another thread and we didn't find it], and since the thread is "closed" we are posting it here...

Basically, the solution is very straight-forward: Install the udev package.

While that sounds straight-forward, Debian-blows-dogs-for-quarters has [again] gone out of their way to make the administrators life as difficult as possible by making sure that there is no apparent way to navigate to 'stable' distro from the 'untable' distro, and furthermore there is no clea way to select which Debian-POS distro you want to get .deb packages from. There appears to be no way to do a substring match when seraching packages. And there seems no way to either know which distro (eg.. 'stable', 'unstable', etc) the packages installed on a given machine came from, either.

And now IceWeasel-POS is crashing - randomly deleting characters from the textarea on blogger.com, and taking a good .7sec per charcteer typed to echo the characters typed - andddddddddddddddddddddddddddddddddddddddddddddd this with dysfunctional spell checking! Also, as you can see, the IceWeasel-POS is repeating characters and words randomly when blogger does its autosave operation.

So this is like : I'm typing a sentence, then stopping and waiting fffffffffffffffffffffffor the words to appeare. - and when they do- the repeats.

We have [sort of] found a solution. Note that in the log below, the 'apt-get install udev' command output is from the second run of same command. Ran it, then ran it again. Not sure why, but it worked.

root@juggalo:/dev# apt-get install udev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  bluez-bcm203x hotplug
The following NEW packages will be installed:
  udev
0 upgraded, 1 newly installed, 2 to remove and 2 not upgraded.
Need to get 263kB of archives.
After unpacking 471kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://ftp.de.debian.org stable/main udev 0.105-4 [263kB]
Fetched 263kB in 1s (183kB/s)
Preconfiguring packages ...
(Reading database ... 139905 files and directories currently installed.)
Removing bluez-bcm203x ...
dpkg: hotplug: dependency problems, but removing anyway as you request:
 atmel-firmware depends on udev (>= 0.070-3) | hotplug (>= 0.0.20040329-12); however:
  Package udev is not installed.
  Package hotplug is to be removed.
Removing hotplug ...
Selecting previously deselected package udev.
(Reading database ... 139875 files and directories currently installed.)
Unpacking udev (from .../archives/udev_0.105-4_i386.deb) ...

**************************************************************
* Please purge the hotplug package!
* (/etc/init.d/hotplug has been found on this system)
**************************************************************

Setting up udev (0.105-4) ...
Installing new version of config file /etc/init.d/udev ...
Installing new version of config file /etc/udev/links.conf ...
Installing new version of config file /etc/udev/persistent-input.rules ...
Installing new version of config file /etc/udev/persistent.rules ...
Installing new version of config file /etc/udev/cd-aliases-generator.rules ...
Installing new version of config file /etc/udev/udev.rules ...
Installing new version of config file /etc/udev/devfs.rules ...
Installing new version of config file /etc/udev/hotplug.rules ...
Installing new version of config file /etc/udev/permissions.rules ...
Installing new version of config file /etc/udev/persistent-net-generator.rules ...
Installing new version of config file /etc/scsi_id.config ...

Note that it is not clear how or why bluez-bcm203x hotplug got installed - it was not requested or wanted, as this machine has no Bluetooth devices, and probably never will.

Other notes of note:

  • The udev package was already installed, but wasn't working right.
  • The installed version of udev did not include the documentation that was [according to the Debian udev package description] supposed to exist in /usr/share/udev/
  • As with so many other Debian-POS commands, there was no man page installed, despite the fact that 'apropos udev' showed a number of [non-existent] man pages for the command. This seems to be a pervasive problem with this particular Debian-lies-like-a-whore distro - many [we're inclined to say "most" actually] of the administrative manual pages are notably missing, even though 'apropos' claims they are there - perhaps there is some issue with the configuration of the 'makewhatis' cron job on Debian-blows? Why would these man pages be left out? And if they are going to be left out, why lie about it through apropos?

So yes, we seem to have fixed this problem, but Debian still sux0r.

Fed Up (rant)

Okay, I've had it - I am fed up. Debian Linux is crap - pure, unadulterated crap. Furhermore, it is crap like Debian that is giving Linux such a bad name. Nothing works on this distro. Nothing. These are not hardware problems, since most of the stuff work under e.g. WINDOWS or fraking SUSE Linux 9.1 - NINE POINT ONE, fer godx sake - that's what, 4 years old now, 5? SuSE 9.1 still uses the 2.4.x kernel, fer fux sake. Yet SuSE 9.1 has some functionality - it "just works".

Since installing this Debiian crap, nothing on this machine works - from the USB drive (won't mount - Debian records in /var/log/messages that the drive has been plugged in and all is well, but all attempts to use the mount command fail with a "Special File /dev/sdXX not found" error. It's true, they're not there (the /dev/ files). Where did they go? They were there yesterday (at least for a little while); they were there about 20 minutes ago when this same machine was running KNOPPIX from a LiveCD image (same source from which I so unfortunately installed this alleged OS called "Debian" - I will refer to it henceforth as "Debian-piece-of-crap" or "Debian POS" for short - [note that this is a run-on sentence which refers back to the "- from the USB dirve ..."] - to the freaking spell-checker in this stupid IceWeasel browser. As I type this, every word in the text input area is flagged as a misspelling - EVEN the ones that I specifically told StoopidWeasel to "Add to Dictionary" - simple shit like "for" and "to" and "an" and "the" and so on. WtF? "Check-as-you-type" spelling? Konqueror has had it for several versions/years now. Freaking MS WORD has it. AND IT WORKS [sort of, in word, but still].

I've heard for years now how Debian such a l33t "engineers" distro - I fought with obsolescent Debian versions in the lab, at work, thinking to myself "there has to be a good reason they chose this lame bullshi over [fill-in-the-blank-distro] that works" - I've [sort of] followe the FOSS debates where all the acolytes sing hoseanah to the great Debian-ness and how "at Debian they are really committed to FOSS."

I call bullshit. Debian is crap, and anyone who doesn't realize it is jst sucking up to the emporer, every bit as the tailors who pretended to make a suit. Linux is the emporer, Debian are the tailors, and the emporer has no clothes. Deal with it.

Now please excuse me while I go find and install a distro that actually works with some of this hardware that apparenlty is just to newfangled a gee-whiz-bang for Debian to have gotten around to - stuff that everybody else was supporting out-of-the-box 8 or 10 years ago - okay, maybe 5 or 6 years, but still...

And finally, I want to make as clear as possible the information that the Debian Package management tools [such as they are] a clearly sub-standard, inferior, user-unfriendly, and just generally suck ass compared to any other modern computing system standard of which I am aware.

I will never again reccomend Debian to anyone [except perhaps to enemies], and will not bother with the excuciating downloads of this Debian crapware. And KNOPPIX - well, you have mislead us all, KNOPPIX - all your fiddling and fixing to make this Debian bullshit run half-assed normal from a LiveCD - it really shows thru what crap Debian is when the KNOPPIX tweaks have are no there.

One final point - I installed the Debian-piece of crap to /dev/hda4 but that process somehow hosed the saved KNOPPIX LiveCD configuration on /dev/hda1 - there is no apparent way to get it back or to copy it over to the Debian-piece-of-crap partition, so not only does the Debian-piece-of-crap not work, it trashed the most stable configuration this machine has had since WinXP was removed, and didn't bother to either a) warn me it was about to trash my working config, or b) tell me that it had done so once it had hosed both the saved config and the new install.

So knoppix myconfig=/dev/hda1 doesn't work anymore - which I suppose is part of the greater plan by the Debian-piece-of-crtap manufacturers to eliminate Linux as a functional alternative OS.

2007-07-15

Konqueror Crash

Konqueror is :

  1. Hanging while waiting for blogger.com to "Publish" a blog post.
  2. Crashing; Konqueror will crash if - while the "publish" operation is in its infinite refresh loop, loading and reloading the "Please wait while your page is published" message page - the user
    1. opens another Konqueror window
    2. goes to view the blog in the new window [note that the post which initiated the publish operation has been posted - the post has uploaded and the blog has been updated, despite the braindead infinite loop the first window of Kongqueror is stuck in]
    3. goes back to the first window [where the ininfinite refresh loop is going on]
    4. clicks on the Blogger Dashboard link there, in the first window, while the infinite refresh loop is going on

Other info from the Crash Handler:

  • Konqueror [crashed and] threw SIGILL.
  • "The application was asked to save its documents"

Default browser indentification string for this version of Konqueror [note that I have broken the line below at the backslash]:

Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.17; X11; i686; en_US)\
 KHTML/3.5.2 (like Gecko) (Debian package 4:3.5.2-2+b1)

Here is the backtrace data from the crash handler:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231935808 (LWP 4267)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x08f95edc in ?? ()
#6  0xb62d57ae in DOM::checkChild () from /usr/lib/libkhtml.so.4
#7  0xb629e96c in DOM::XMLAttributeReader::~XMLAttributeReader ()
   from /usr/lib/libkhtml.so.4
#8  0xb6268f9e in KHTMLPart::saveState () from /usr/lib/libkhtml.so.4
#9  0xb62289fe in KHTMLPartBrowserExtension::saveState ()
   from /usr/lib/libkhtml.so.4
#10 0xb6875b5f in KonqView::updateHistoryEntry ()
   from /usr/lib/libkdeinit_konqueror.so
#11 0xb6893a11 in KonqView::slotCompleted ()
   from /usr/lib/libkdeinit_konqueror.so
#12 0xb6893c23 in KonqView::slotCompleted ()
   from /usr/lib/libkdeinit_konqueror.so
#13 0xb689987d in KonqView::qt_invoke () from /usr/lib/libkdeinit_konqueror.so
#14 0xb72b8678 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb72b8fdc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb7f85e0a in KParts::ReadOnlyPart::completed ()
   from /usr/lib/libkparts.so.2
#17 0xb62581c0 in KHTMLView::timerEvent () from /usr/lib/libkhtml.so.4
#18 0xb72b5786 in QObject::event () from /usr/lib/libqt-mt.so.3
#19 0xb72f2b9a in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb724e87a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb724f5f5 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb792502e in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb71e0001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb7240305 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#25 0xb71f3d2a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb7267255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb726717a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb724d38d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0xb68be17c in kdemain () from /usr/lib/libkdeinit_konqueror.so
#30 0xb7fb1524 in kdeinitmain () from /usr/lib/kde3/konqueror.so
#31 0x0804e1d6 in ?? ()
#32 0x00000004 in ?? ()
#33 0x080cff68 in ?? ()
#34 0x00000001 in ?? ()
#35 0x00000000 in ?? ()

More about KNOPPIX and the HP a220n

The X log file on the HP Pavilion a220n running KNOPPIX:

uploads/Xorg.0.log.TXT

This file is found at /var/log/Xorg.0.log on the system while the system is running.

Getting 'sudo' Working

There is a simple bit of information that has finally penetrated the fog of insanity that surrounds computers and related equipment that information is this:

When using the sudo command under Linux [don't know about other systems, yet] it is the case that users who are listed in the /etc/sudoers file actually use their own account password to execute the sudo command, not [as some of use might have once thought] the root account password as is used when accessing the root account with the su command.

This information has now been shown to be true under systems that include, but are not limited to:

  • KNOPPIX (with passwords and user accounts enabled
  • Debian
  • CentOS

Full dmesg Output for a220n under KNOPPIX

Capture of the output of the command dmesg performed under KNOPPIX on the HP Pavilion a220n:

Here is the output of uname -a for this same system:

Linux Knoppix 2.6.17 #4 SMP PREEMPT Wed May 10 13:53:45 CEST 2006 i686 GNU/Linux

Audio Problems on HP Pavilian a220n under Debian Linux

This is an excerpt from the output of the lsmod command run under KNOPPIX on an HP Pavilion a220n desktop computer:

snd_intel8x0           31260  3
snd_ac97_codec         88352  1 snd_intel8x0
8250_pnp               12288  0
snd_ac97_bus            6016  1 snd_ac97_codec
snd_pcm_oss            38176  0
snd_mixer_oss          17536  1 snd_pcm_oss
snd_pcm                73220  4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer              22148  2 snd_pcm
shpchp                 37032  0
i2c_nforce2             9856  0
snd                    44768  10 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer

For some reason neither KNOPPIX 5.0.1 nor the Debian install to the hard disk [provided by the KNOPPIX LiveCD via the knoppix-installer command] seem to be able to get the audio input functionality of the sound card working.

Audio output works okay when the Sound System is enabled via the KNOPPIX control panel, but does not appear to work under the Debian instantiation of KDE.

No version numbers captured yet from the Debian kernel, or the versions of KDE involved (which are different between the Debian install (with updates) and the KNOPPIX distro.

2007-07-11

MSN Proprietary Wink Protocol?

Has anyone put a protocol sniffer on the MSN protocol lately? I'd like to have the protocol definition for the proprietary winks [shown in photo as rendered in Pidgin IM client v2.0.2 ] - or maybe they're filtering on the server? Can I spoof the IM client ID to the MSN server?

Zoom the screenshot to read the text ad sent by MSN servers to my IM client when the person I was chatting with sent a [apparently proprietary to MSN] "wink"

Note that Pidgin IM client is the former Gaim IM client for windows, AND that Pidgin's domain is the first instance I've seen of a working .im TLD [it is pidgin.im]

[And: props to my new sweetheart for sending that wink which highlighted this issue for me - apparently no one else talks [types] to me quite like that, kittykitty]