Woohoo! the Slackware site is back and jamming! As so often is the case, my panic was for nothing.
That is all,
Stu…
Woohoo! the Slackware site is back and jamming! As so often is the case, my panic was for nothing.
That is all,
Stu…
Yesterday, I noticed that the site slackware.com seems to be missing. Instead of the beautifully simple normal site, I see a silly parked-domain-style landing page. Eeek!
After a little poking around, I found the server still holding the real site at: http://64.57.102.34/
Perhaps I panicked. My hope is that this update to the DNS entries for slackware.com is a mistake, an oversight. It is, after all, the holidays and I’ve heard that some people do have lives!
Happy New Year!
Stu…
P.S. I finally noticed the notice: “slackware.com expired on 12/25/2010 and is pending renewal or deletion” on the parking page. Since the whois info shows an update on 12/31/2010, I hope this means that the issue is currently being resolved!
I have never liked the idea that the three Rs are reading, ‘riting, and ‘rithmatic.
The saying may be cute, but writing and arithmetic don’t even begin with the letter r! Sheesh! When referring to education, one should strive to use correct English, right!?!
Anyway, for me the three Rs are: Reduce, Reuse, and Recycle.
With world population growing and resources dwindling, making the most of the resources we consume seems reasonable: a simple and effective contribution to the future of the human race.
The first step is to reduce. Take care in choosing products that use less packaging. If an excellent product uses too much packaging, let the company know. Tell them that they have a great product and that if they reduce packaging you will continue to buy it. (There is no reason to threaten them: just give them the opportunity to join in the effort for sustainability!)
The second R is reuse. One of the items we reuse most is plastic bottles. Soda and water bottles can be reused over and over. I make my own bottled water using left-over water bottles and water from a filtering picture. Considering that standards for tap water are higher than those for bottled water. So, my filtered tap water is quite likely better than most bottled water and at a fraction of the cost of bottled water.
Junk mail is is fun to reuse. I enjoy taking notes and making shopping lists on the back of junk mail. When I’m done with the paper I can employ the third R: recycling!
Most large communities already have some form of recycling. Where we live, the city provides a bin in with which we can recycle paper, plastic (with recycle numbers of 1 or 2) and glass. The beach town where have often vacationed has recycling centers, where one may drop of paper, plastic and glass. Check to see what types of recycling are available in your community. If none exist, consider starting a recycling program in your neighborhood or ask the local government how you can help them join the recycling world.
So far I’ve only included dos; now a big don’t:
<rant>
Juice boxes are evil: the amount of packaging compared to the amount of juice is completely unreasonable! Besides, it’s much cheaper to make juice from frozen concentrate, then store and serve it in used plastic bottles. The bottles can be washed and reused many times; and the bottle becomes cloudy it can be recycled.
</rant>
With very little effort, we can make a huge contribution to the world. We can reuse stuff rather than just throw it away. We can reduce the amount of packaging we buy and reduce the amount of trash we send to the dump. Finally, we can recycle our old paper, cardboard, plastic and glass.
Even if you’re not a tree-hugger, you can spend less time and effort taking out the trash, by producing less trash!
Life is good; share it with the future!
Peace,
Stu…
When I upgraded Google Chrome to version 6.0.472.53, borders appeared around the window: these borders were not there when I was running version 5.x and I was not happy!
After wasting much time creating a Window-Specific behavior–causing my KDE theme’s minimize, maximize and close buttons to disappear–I realized that what I was looking for was actually a setting in Chrome’s options. Color me red!
To make Chrome 6.x look like it did in the 5.x days, select Options from the Customize and control Google Chrome widget (the little wrench on the right:
). Click on the Personal Stuff tab, under Appearance, select the Hide system bar and use compact borders radio button:
Ah, things are much better now . . . at least back to the way to which I have become accustomed!
Happy Hacking!
Stu…
After the latest round of updates to Slackware64 13.1, compositing died on my machine. The first thing I noticed is that my windows no longer wobbled.
When I checked in System Settings -> Desktop -> Desktop Effects, I saw that “Compositing has been suspended by another application . . .” I clicked the Resume Compositing button, but once again received the message and found that “Compositing is temporarily disabled.”
After a bit of searching, I found a post on the KDE Community Forums where a Kubuntu user had solved this issue by checking Disable functionality checks on the Advanced tab. Figuring it was worth a try, I checked the box and clicked the Apply button. Oops! My desktop became pale blue nothing!
Using the CTRL+ALT+BACKSPACE key combination, I shut down X. Then, from the shell, I poked around my .kde directory and found the setting in .kde/share/config/kwinrc as “DisableChecks=true.” So, I removed this line from the file and started X once more: still no compositing; no effects, but at least I had usable KDE. (See: there’s a good reason I don’t start the GUI automagically!)
At this point I was mildly frustrated. I couldn’t understand why upgrading Xorg server to 1.7.7 killed compositing. Heck, maybe was it the newly installed kdegraphics-4.4.3!?! Did I really want to fuss with reverting packages until the problem went away? Nope!
I figured it was time to punt, so I downloaded and installed the latest nVidia driver–as much to give my self something to do as in hopes that it would fix the problem. Once the driver was installed, I logged out as root and logged back in as myself. Now the moment of truth! I typed startx and pressed my well-worn ENTER key. OMG! It worked! I have wobbly windows again!
So, time to check this on the MacBook which uses an nVidia 9400M. Same results: no compositing after the upgrade and upgrading the nVidia driver fixed the issue.
The TL/DR of it all is: If upgrading Slackware kills your nVidia card’s compositing, just update the nVidia driver to 256.44 and life is good!
Happy Hacking!
Stu…
P.S. I was previously using nVidia driver version 256.35.
Attention-grabbing headline, eh? Well, that’s what this project feels like.
After learning to use CloneZilla Live to create and restore system images, booting from a customized CD with images on external USB hard drives, I decided to install CloneZilla the USB hard drive and get the CD out of the equation.
I found a very useful page describing the process of installing CloneZilla Live on a hard drive on the CloneZilla site. I used these directions to copy the .zip file into a Linux partition. Alas, the directions for making it boot use grub; Slackware and I still use LILO.
So, armed with these directions, I figured out how to boot the copied CloneZilla live using LILO.
While installing Slackware 12.2 on another partition on the hard drive, I set LILO to boot Slackware, ignoring CloneZilla for now.
Then, I created the directory /live-hd/ on the Slackware partition and copied vmlinuz and initrd.img there.
After much experimenting, reading LILO man pages, and twiddling with Slackware’s /etc/lilo.conf, I ended up with this:
image = /live-hd/vmlinuz root = /dev/sda1 initrd = /live-hd/initrd.img vga = 788 addappend = "boot=live union=aufs live-media-path=/live-hd bootfrom=/dev/sda1 toram=filesystem.squashfs" label = CloneZilla read-only
So, there you have it! The LILO spell for booting CloneZilla Live from /dev/sda1
Phase II of the project will be turning the “Live” system into a normal Linux system that doesn’t recreate itself each time it boot. Hence: Killing CloneZilla Live!
Enjoy!
Stu…
This is the tale of how I screwed up a domain transfer and gained the opportunity to experience the excellent support provided by Register.com.
My first mistake was missing the email containing the domain transfer spells–Transaction ID and Security code–from GoDaddy.com transfers. The person to whom I am transferring told me that his account showed the transfer still “awaiting approval.”
So, I logged on to Register.com to see what I could see. This lead to my second mistake and much frustration on my part:
Poking around the domain information, I see: “Transfer of registrant feature is locked for your account. Please see our FAQs or contact Customer Support for more information.”
OK, so I read the FAQ. It instructs me to download a form, fill it out and fax it back. So, I did. I waited an hour and called Register.com tech support to find out how long this will take. I spoke to a very nice gentleman who took the time to see if the fax had been received. It had, but the poor quality of the fax made it impossible for them to process.
By this point, I’m getting upset. Why on Earth should I have to fax a photo ID and fill out a form just to transfer a domain. (I didn’t: that was my second mistake! I’ll get to that in a minute.)
The tech support person offered to help expedite the transfer of registrant. If I would send a readable version of the fax, he would walk it through. I expressed my frustration as the complexity of this transaction. He remained calm and helpful.
I scanned my drivers’ license at extremely high quality and inserted it into the PDF. I completed the rest of the form, printed it, and faxed it to Regsiter.com. That was enough for one day, so I went on to other things, taking the opportunity to complain to our student workers how difficult they were making a process that I believe should be quite simple.
The following morning, I received an email from Register.com saying that the second fax did not prove that I was the legal entity to whom the domain was registered. I also received an invitation to take a survey about my experience with Register.com support. Oh, goody!
I filled out the survey, answering truthfully that the support person was nice, knowledgeable, and helpful. Then, under the whatever else you wanna say portion of the survey, I blasted Register.com for making the transfer process so complicated and vowing to tell everyone that would listen to “avoid them like the plague!”
I started work on the third version of the fax, in an attempt to prove to them that I was really me. Before I could finish scanning and inserting a second photo ID, my phone range. It was Regsiter.com support.
A very nice and helpful woman explained to me that the domain was originally registered to an organization and that I needed to prove that I was a duly appointed representative of that organization. I did not yell. I attempted to explain how frustrated I was and that the organization to whom the domain was registered was a grant project, and not a legal entity by whom I could be duly authorized. I told her I had registered this domain and it shouldn’t be so complicated to transfer it to another person. She remained cheerful, supportive, and helpful.
After a short while and some excellent questions on her part, she realized that I was trying to change the registrar and not the registrant. Yes, I got confused about the terms and was working on entirely the wrong process! (At this point, you’ll want to imagine me turning red and apologizing profusely.)
She offered to expedite the process once the person to whom I registered the domain finished his end of the transfer. She waited patiently on the phone while I located the email I had missed the previous day. I thanked her profusely, apologized again, and set about taking responsibility for my confused and rather harsh actions.
The first step was to tell the folks to whom I complained about Register.com that the mistake was mine. I told them all–all three, that is–as soon as I saw them.
The final step is to write this blog entry, explaining that Register.com has great tech support: they really do! Their support is a toll-free call (at least for my location in the United States).
Update: As of 14:16 EDT US, the Google search page is back to normal. Hooray!
This morning I find that www.google.com now has a background image that I hate! From what I can tell, the only way to get rid of it is to sign in with a Google account. WTF?!?
Let me think . . . Do I want the company that is in the hot-seat for accidentally collecting WiFi data with the Street-view cars to link all my searches to an account? I think not!
Update: According to Google employee Paul, this celebration will only plague us for one day. For those who aren’t celebrating, I created a minimal search page on Bovitron.com. Enjoy!
Grrr on companies that think they know what I want better than I do!
While testing out Slackware64 13.1, I found that VMWare Workstation doesn’t like kernel 2.6.33.4.
Installing VMWare workstation from the bundle worked fine, but it won’t run because the VMWare modules don’t compile. Running vmware-modconfig –console –install-all gives the cryptic message: “gcc and kernel headers must be installed.”
Um, gcc and the kernel headers are installed!
After a little digging, I found this VMware Fusion 3 on Mac OSX howto posted by Chris Willing at The University of Queensland Visilab: http://www.vislab.uq.edu.au/howto/vmware.html
This gave me my first clue: the files autoconf.h and utsrelease.h have moved from include/linux to include/generated. As much as I hate to hack my kernel source, I opted to link these files in include/linux.
cd /usr/src/linux/include/linux/ ln -sf ../generated/autoconf.h . ln -sf ../generated/utsrelease.h .
Now vmware-modconfig –console –install-all runs, but fails on compiling the vmnet stuff:
/tmp/vmware-root/modules/vmnet-only/vnetUserListener.c:240: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function)
To fix this, I found the define for TASK_INTERUPTABLE (in /usr/src/linux/include/linux/sched.h). Now, to tell vnetUserListener.c about it:
cd /usr/lib/vmware/modules/source/ cp vmnet.tar was_vmnet.tar cd ~/tmp tar xf /usr/lib/vmware/modules/source/vmnet.tar cd vmnet-only
In vnetUserListener,c, add the line: #include <linux/sched.h> after #include "vnetInt.h"
cd .. tar cf vmnet.tar vmnet-only mv vmnet.tar /usr/lib/vmware/modules/source/
Now vmware-modconfig –console –install-all dies on the vmci stuff. As Chris Willing noted in the VMware Fusion 3 on Mac OSX (see above), adding a line to pgtbl.h fixes this:
cd /usr/lib/vmware/modules/source/ cp vmci.tar was_vmci.tar cd ~/tmp tar xf /usr/lib/vmware/modules/source/vmci.tar cd vmci-only/include
In pgtbl.h, add the line: #include <linux/sched.h> after #include "compat_page.h"
cd ../.. tar cf vmci.tar vmci-only mv vmci.tar /usr/lib/vmware/modules/source/
Finally, it all compiles and we have a working VMWare Workstation install!