also
Thursday, November 13 2014
[20:27:53]
matt [wronka.org]/Lilith
Also annoyingly with CM11 Trebuchet cannot rotate and widgets cannot be resized.
Sunday, April 21 2013
[19:14:11]
matt [wronka.org]/Psi.generay
Michael Spellman said he bought tickets to Saturday’s Red Sox game at Fenway Park to help send a message to the bombers.
‘‘They’re not going to stop us from doing things we love to do,’’ he said, sitting a few rows behind home plate. ‘‘We’re not going to live in fear.’’
http://www.boston.com/news/nation/2013/04/21/interrogators-wait-question-bombing-suspect/uFBMZr3aHZSHtsIYJhTfpN/story.html
Also an important point from that article:
ACLU Executive Director Anthony Romero said the legal exception applies only when there is a continued threat to public safety and is ‘‘not an open-ended exception’’ to the Miranda rule, which guarantees the right to remain silent and the right to an attorney.
The federal public defender’s office in Massachusetts said it has agreed to represent Tsarnaev once he is charged. Miriam Conrad, public defender for Massachusetts, said he should have a lawyer appointed as soon as possible because there are ‘‘serious issues regarding possible interrogation.’’
‘‘They’re not going to stop us from doing things we love to do,’’ he said, sitting a few rows behind home plate. ‘‘We’re not going to live in fear.’’
http://www.boston.com/news/nation/2013/04/21/interrogators-wait-question-bombing-suspect/uFBMZr3aHZSHtsIYJhTfpN/story.html
Also an important point from that article:
ACLU Executive Director Anthony Romero said the legal exception applies only when there is a continued threat to public safety and is ‘‘not an open-ended exception’’ to the Miranda rule, which guarantees the right to remain silent and the right to an attorney.
The federal public defender’s office in Massachusetts said it has agreed to represent Tsarnaev once he is charged. Miriam Conrad, public defender for Massachusetts, said he should have a lawyer appointed as soon as possible because there are ‘‘serious issues regarding possible interrogation.’’
Tuesday, October 18 2011
[04:16:26]
matt [wronka.org]/Vasilissa
I've set-up a Debian chroot in parellel with Ubuntu (both thru the preware packages), and while Ubuntu has some newer packages in theirs, the Debian Iceweasel is actually stable, unlike Ubuntu Firefox. Also, in Ubuntu, I could not find the option to snow a menu in Psi with left click, which makes much more sense when I only have one mouse button in effect.
Saturday, October 1 2011
[05:15:30]
matt [wronka.org]/Merch
The fruit plates many of these places are bringing on check-in are very dissapointing. Also, the lack of drink available.
[18:43:33]
matt [wronka.org]/Merch
The Charisma has an annoying captive portal which means a) only one device (and one person) per room can use the network, and that when the session times out, it will poison your DNS cache so that you cannot access the Web site or machine you requested for a while. Also, the access point seems to be incredibly flakey and drops every couple of minutes at best.
Friday, May 27 2011
[03:19:32]
matt [wronka.org]/Merch
Also, apparently I had been running ejabberd and not openfire.
Monday, April 25 2011
[13:20:37]
matt [wronka.org]/Merch
Also remarkable, this is the first time I've ever received SATA cables in the box.
Saturday, February 19 2011
[18:20:54]
matt [wronka.org]/Merch
Also...
Friday, May 28 2010
[13:41:11]
matt [wronka.org]/tkabber
So the last comment was out of frustration. The OS was hosed from the apt-get failures:
<prox> So this is all a result of the dist-upgrade?
> Sort of.
> It's a result of the root filesystem being too small indirectly.
> The previous update failed; PR1.1 back in February.
> I did some cleaning and manual directory restructuring to clean that up, but the updater didn't like that it had failed. apt-get dist-upgrade installed the components after that, but I don't think it ever
+really realized what version of Maemo it was running after that.
> It didn't even *know* there was an update when PR1.2 came out this week. I think it'd borekd something.
> And so I did an apt-get dist-upgrade and it ran out of disk space again.
> http://quec.es/org.wronka/matt/2010/05/27/
> 154MB in /usr/lib on a 255MB root partition.
<prox> Uhhh..
> I'd been able to remount /usr/share and a few thigns on /var off of the 2GB /home partition.
> but I couldn't do much with /usr/lib because it was in use ... I probalby should have just tried cleaning-up the microb-engine.
> But yeah; directly, the apt-get dist-upgrade failed a lot, and I wasn't able to fix it. Also, damned if I don't know what some of the config collisions really meant.
> but my N900 is flashed and running. yay.
> (That was quick!) Let's see if I can find my data.
> Hah! the zimbra connector or whatever it is ... mail for exchange ... is working !
> My dada is safe
> for now....
<prox> So this is all a result of the dist-upgrade?
> Sort of.
> It's a result of the root filesystem being too small indirectly.
> The previous update failed; PR1.1 back in February.
> I did some cleaning and manual directory restructuring to clean that up, but the updater didn't like that it had failed. apt-get dist-upgrade installed the components after that, but I don't think it ever
+really realized what version of Maemo it was running after that.
> It didn't even *know* there was an update when PR1.2 came out this week. I think it'd borekd something.
> And so I did an apt-get dist-upgrade and it ran out of disk space again.
> http://quec.es/org.wronka/matt/2010/05/27/
> 154MB in /usr/lib on a 255MB root partition.
<prox> Uhhh..
> I'd been able to remount /usr/share and a few thigns on /var off of the 2GB /home partition.
> but I couldn't do much with /usr/lib because it was in use ... I probalby should have just tried cleaning-up the microb-engine.
> But yeah; directly, the apt-get dist-upgrade failed a lot, and I wasn't able to fix it. Also, damned if I don't know what some of the config collisions really meant.
> but my N900 is flashed and running. yay.
> (That was quick!) Let's see if I can find my data.
> Hah! the zimbra connector or whatever it is ... mail for exchange ... is working !
> My dada is safe
> for now....
Thursday, May 6 2010
Maemo Developer List : "Why should I write apps for Maemo?" posted by Michael Cronenworth
[14:48:12] matt [wronka.org]/kerberos Mr. Michael Cronenworth recently posted a well-worded question directly to the Maemo development community (and Nokia indirectly) which echos much of the sentiment around Maemo and the N900 right now. Personally, I love the devices promise, I like the software, but I wish Nokia were a bit more open with the community (release early, release often being just the start).
His missive read:
«The continued delay of PR 1.2 has caused me to pose this question.
Without customized packaging, I cannot reliably publish applications to
the global maemo.org repositories at this time. Also having APIs in flux
without knowing when the new version is coming out makes me even less
interested. Sure, you can compile a new kernel or create a trivial
application all day long and ship it today, but I wish to write some
rather advanced applications that cover a broad range of APIs.
At most, the SDK should have been released two weeks ahead of the final
release. With a little over a month now on the clock, people can only
begin to speculate as to how poor Nokia's release management is working.
I, as a software developer, realize that unexpected issues can occur
causing unexpected delays, so this e-mail is not a "Nokia hurry up"
plea, but a concern that developing for Maemo requires a serious
commitment to add checks for multiple versions of APIs and packaging
requirements.
If I relied on the ability to publish commercial applications to the Ovi
Store, I'd be living in the street. It's been six months and the Ovi
Store for Maemo is still without a commercial solution and is extremely
limited in general.
In closing, I have a few questions to propose since communication from
Nokia in general is hit or miss (some are better than others, I realize):
-Why was the PR1.2 SDK released at the time it was released?
-If there will be any updates >PR1.2, have there been discussions on
changing the staged release of the SDK?
-Is PR1.2 still going to be released? (I am not looking for a release date)
-Where are those Ovi Store applications that we have been taunted with
videos of?
-Will there be a commercial solution with the Ovi Store or should I
expect to create my own retail store?
Michael »
The delay in the release of PR1.2 has caused problems (and for a long time completely prohibitted any) applications from being updated on the device since the build environment was using an incompatible API from the end-user devices.
[14:48:12] matt [wronka.org]/kerberos Mr. Michael Cronenworth recently posted a well-worded question directly to the Maemo development community (and Nokia indirectly) which echos much of the sentiment around Maemo and the N900 right now. Personally, I love the devices promise, I like the software, but I wish Nokia were a bit more open with the community (release early, release often being just the start).
His missive read:
«The continued delay of PR 1.2 has caused me to pose this question.
Without customized packaging, I cannot reliably publish applications to
the global maemo.org repositories at this time. Also having APIs in flux
without knowing when the new version is coming out makes me even less
interested. Sure, you can compile a new kernel or create a trivial
application all day long and ship it today, but I wish to write some
rather advanced applications that cover a broad range of APIs.
At most, the SDK should have been released two weeks ahead of the final
release. With a little over a month now on the clock, people can only
begin to speculate as to how poor Nokia's release management is working.
I, as a software developer, realize that unexpected issues can occur
causing unexpected delays, so this e-mail is not a "Nokia hurry up"
plea, but a concern that developing for Maemo requires a serious
commitment to add checks for multiple versions of APIs and packaging
requirements.
If I relied on the ability to publish commercial applications to the Ovi
Store, I'd be living in the street. It's been six months and the Ovi
Store for Maemo is still without a commercial solution and is extremely
limited in general.
In closing, I have a few questions to propose since communication from
Nokia in general is hit or miss (some are better than others, I realize):
-Why was the PR1.2 SDK released at the time it was released?
-If there will be any updates >PR1.2, have there been discussions on
changing the staged release of the SDK?
-Is PR1.2 still going to be released? (I am not looking for a release date)
-Where are those Ovi Store applications that we have been taunted with
videos of?
-Will there be a commercial solution with the Ovi Store or should I
expect to create my own retail store?
Michael »
The delay in the release of PR1.2 has caused problems (and for a long time completely prohibitted any) applications from being updated on the device since the build environment was using an incompatible API from the end-user devices.
Saturday, March 27 2010
[18:55:31]
matt [wronka.org]/0d9e873f
Also, NFS hangs on the N900 in maemo. I haven't tracked this down yet or looked for an open bug.