Why has this art-form escaped my notice for so long?!





I love the fluidity of the medium and how closely it relies on good drawing skills. It's almost like drawing but with a solid 3d pencil in 3d space. The most challenging ones are perhaps done with a single roll of wire seamlessly flowing into forms and shapes. It's almost origami but with wire... Fascinating!

But this one?

BIG OUCH!

---

From:

It's STILL ONLY FRIDAY!
It's the weekend of hope.

I will.
-- Finish my tasks and reach my goals this weekend.
-- NOT be distracted by ANYTHING.
-- Check in with my progress here.
-- Make sure than I am on track.

Tasklist

1. Mcombinations
2. Equivalence coding
3. Ratio decision.
4. Extraction.
5. Function port.
6. Covariable recognition
7. Variable selection (D)
8. a) conventional
9. b) bootstrap
10. Variable selection (W)
11. a) conventional
12. b) bootstrap
13. Model evaluation (D)
14. Model evaluation (W)
15. Send to A/M/Z

---

1. SNP Scoring
2. Run through algorithm
3. Send to R

The latest pulseaudio debian repositories are at this:

I hope they fix the low-volume-through-front-speakers issue I have been having with the older versions...

NOTE: This was a bad decision. Stick to the repository version.

If you don't have much time to stand around stirring the onions and want to caramelize onions perfectly with the least amount of work...

3 minutes prep:
1. Peel and chop red onions lengthwise. Turn the chopping board and chop the lengthwise chopped onions into three.

2. Toss in olive oil, salt and spices

40 minutes cooking time (unattended).
3. Spread on a stainless-steel cookie sheet in an even uniform layer. Roast at 375 deg F for 40 minutes.

Perfectly caramelized onions ready to go into whatever you are cooking... or maybe even as a fun dinner with a little lime juice and chopped apples.

---
PS: The method doesn't work so well without
a) salt (because then, the onions become very dry and may burn/char instead of caramelizing).

b) stainless-steel cookie sheets. The non-stick varieties are just awfully non-uniform when it comes to heat conductance. I have always had partially charred results with those.

A while back, I wrote about how I was under-utilizing (e:strip). (e:tinypliny,54394). I am constantly making notes all over the internet and it becomes so crazy to keep track of everything. So I have decided never to log out of here and make all those notes here (except work) - which is still at citeulike.

I can't transfer all work here because then (e:strip) would also have to be my reference manager and store my million pdfs... Yeah, not very practical.

The thing is the search function of (e:strip) sometimes does not play well with my blogs. I don't know what to do about that. My one big request/feature-suggestion for (e:strip) would be to make search results somehow more accessible and context-sensitive along with the ability to use more search-modifiers... maybe.

And while we are on the subject of search, one more suggestion would be to turn up blog-numbers, or cite-able referral links along with the blog titles and excerpts in the search results. For example

Using (E:strip) To Its Potential...
06/01/11 @ 11:20 (e:tinypliny,54394)
excerpt with keyword visible here

Cross-referencing would become so much easier. Currently, I hover my mouse over every post to find out the number and then string it to the name of the (e:peep) who wrote it. Makes for a longer workflow.

(or how Google is everyone's mother(tm) (e:Paul), 2011)

I think (e:mrdeadlier) did this once but there is now a site for finding out what Google thinks of you.

Let's see: Who is tinypliny?

tinypliny is the network based installer
tinypliny is the minimalistic one that does not even
tinypliny is the
tinypliny is an unknown quantity at this point
tinypliny is offline
tinypliny is that a sweater with the shorts?

Who are you according to Google? Find out at this

---

PS: Who or what is Binky?

I kind of like being on Linux, now that my wireless is functioning. It's a lot of heartache but somehow it gives you more power over what's going on in the recesses of your computer. It's as if you have found that you can split open a blackbox and are able to look at the virtual software connections and wires that make your computer tick.

Linux = 85% pain + 5% revelations + 10% knowledge everyday.

I just have to decide if the 15% of useful stuff is worth the 85% pain...

Google search... evolving right under your noses (or in front of your noses, as the case may be).


And (e:Paul). Hee Hee. Someone was spying on i2. ;-)

Some stuff you can do for a faster boot time on Crunchbang.

1. Enable autologin.
Open the terminal and type

gksu gdmsetup

You will need to enter your administrator password. Go to the "Security" tab and check "Enable Automatic Login".

2. Decrease grub menu timeout.
Edit the /etc/default/grub file and change the grub option menu timeout to 1 or 0

GRUB_TIMEOUT=1 (or even 0).

Additional random but useful notes that might be helpful to people struggling with existential queries on Crunchbang:
a) Prevent Iceweasel from weaseling in.
I like Google Chrome beta on my OS. But uninstalling the default Chromium compulsorily installs something called iceweasel. One way around this is to install the iceweasel-dummy package to avoid installing iceweasel when you remove chromium. Apparently, there is some java dependency on this neverending it's-either-chromium-or-iceweasel vicious cycle on crunchbang. What a mess.

b) To check if JRE (Java Runtime Environment) successfully installed on your laptop, type the following at the terminal:

find / -iname java -print 2>/dev/null

With my new found "Su" power, I compiled the RTL8191SEvB wireless driver in Crunchbang and am documenting all the (as it turns out, rather minor) hurdles and leaps here. The good news is if I can do it, you can surely do it too. I am pretty much the lowest of the lowest common denominators when it comes to dealing with linux. And no, I am not being humble. Linux and I haven't found much common grounds for camaraderie yet. However, we tolerate each other because we simply have to. The alternatives are even more hideous and strewn with frustrations.

0. Get the driver from the Realtek site at this Get both RTL8192SE and RTL8191SE-VA2 if you are doubtful of what to get.
Special Note: Pay attention to which version of the driver you are downloading. First check your kernel version with:

uname -r

Then pick either
--> Linux driver for kernel 2.6.34 (and earlier) or
--> Linux driver for kernel 2.6.35 (and later)
depending on what version came up with uname -r. I am telling you based on my bitter experiences that you will end up wasting a ton of time if you download the wrong version.

1. Crunchbang has a problem with su and can't really switch you into Su root mode unless you do this: At the terminal type:

sudo su

followed by

passwd

The system should now ask you for a new root user password. Enter something that you will remember. You are set with a Su command to go into root mode like in regular debian.

2. Type the make command at the terminal:

make

If you have a vanilla no-frills crunchbang installation "make" is sure to complain with:
make: *** /lib/modules/2.6.32-5-amd64/build: No such file or directory. Stop.
make: *** [all] Error 2

2a. It's whining about the lack of kernel headers so install the kernel headers:

apt-get install linux-headers-2.6.32-5-amd64

(...which makes you wonder why the kernel was headless to begin with. Perhaps to save space. Perhaps to add to your vexation. Who knows.)

--
Note: If you want to install these headers manually, these are the files you need from the debian repository:

• linux-headers-2.6.32-5-common_2.6.32-31_amd64.deb
• linux-kbuild-2.6.32_2.6.32-1_amd64.deb
• gcc-4.3_4.3.5-4_amd64.deb
• gcc-4.3-base_4.3.5-4_amd64.deb
• cpp-4.3_4.3.5-4_amd64
• linux-headers-2.6.32-5-amd64_2.6.32-31_amd64.deb
• linux-headers-2.6-amd64_2.6.32+29_amd64.deb

In that order.

---

3. You can then go ahead and issue the make command again:

make

. A ton of mumbo-jumbo will scroll across your terminal but most of it will be orderly except this line:

/rtl8192se_linux_2.6.0019.1207.2010/HAL/rtl8192/rtl8192s/r8192S_firmware.c:722: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘long unsigned int’

Some not-very-consequential warning. I am told it could be because of the carelessly or poorly written code for the driver. Which is also claimed as the reason (by debian overlords in the #debian channel on the irc.debian.net server) why it was not included in the native Debian kernel and is only scheduled for inclusion in the 3.0 version after some squabbling or quality checks or both... or none. Again, who knows what's going on the dark recesses of kernel-developers minds.

4. Assuming, there are no other warnings and errors (there were none in mine), issue the make install command:

make install

Another scroll of messages where linux will enter and exit various directory locations will follow. Hopefully these entries and exits will pass without incident. If there is some permission error, you probably don't have Su power. See step 1. Sudo doesn't cut it for the whiny RTL8191SEvB driver.

5. Finally. SHUT DOWN completely and reboot. Hopefully you will be able to see your wireless networks now. If not, you have probably wasted your time reading these instructions and it's time to go and read the other zillion forum posts about this difficult wireless driver on the rest of the net. Even if none of them end up helping you, they would have, at the very least, taken a shot at helping build some character - which you will need for putting up with no wireless in a laptop.