Being a geek, you know, I want to meet other geeks, and to be honest, I havent had much luck at all. \
So anyways, I signed up for this “geek” site, they are basically for all “geeks.” Sports, computers, sci-fi, just to name a few. Sounds fine, and dandy.
Sounds good over the rest of the ‘dating’ sites. But there are some bad things that are annoying me.
Lets break it down.
+1 catering to geeks.
+1 making it geek
-type neutral.
-1 Interface
-1 Contact us.
-5 About us.
-1 page/content Layout
-1 contact
Alright im just going to stop there.
So one, the interface. I somehow toggled the “you cant view my hometown” option, and now i am “dan from ,illinois” and i cant figure out how to change it.
the “contact us” page (i was going to ask how to flip that bit) was asking me for my name, email and if i was already a member (i am signed in, DUH)
the layout of everything sucks. its like web 1.0 days, and they repeat the same functions over and over.
contact sucks. everyone, and i mean everyone always sends a welcome email, gk2gk didnt even say “hi”
and heres the kicker, i saw this after i signed up and crap–the about us page. Yaknow, I cant even describe it. visit the link [http://www.gk2gk.com/about/] and watch the video for yourself.
Oh yea, and one last note, firefox kept warning me about unencrypted content on the site. Id be very weary entering in any financial transactions with them.
Really, its not the OS I hate, its not fully the distro (I do hate some things about debian based systems but thats something else).
My problem is with the *buntu zealots. “z0MG I jUSt insTALLed (u|myth|eee|ku|whatever)buntu ANd It IS awESOME!!!111oneone”
“THESE ARE THE COMMON *BUNTU COMMANDS TO LEARN IF YOU WANT TO GET AWAY FROM WINDOWS!”
This and that and everything about hating windows. All-in-all, they keep saying this is for *buntu. They dont mention its compatible with Fedora, or gentoo, or hell, even debian (*buntus are based on debian!!!). No, the guides online are specific to to *buntu….
So, I present to you, my quick and dirty php script that converts *buntu based guides into generic linux non-specific based guides. All by changing the things specific to debian based systems, and adding info for other common package managers.
So as some of you may know already, I bought an eeePC, for fun and to mess around with. Well my latest fun with it was adding a touchscreen, and adding internal bluetooth!
Well, I purchased the Hoda Technology 8.9″ Solderless Easy and Fun TouchKit Touch Screen Kit, which came with a touchscreen, the controller board (with added USB hub) and the wires to connect it solderlessly to a internal USB header (I had one as I do not have a built-in cam, though even if you do, you can still use this!)
Below is a quick guide on what I did to add in the touchscreen:
Here is the contents from the kit, included a dual pen/stylus!
First I took apart my machine following the many guides to make sure I did not break anything I shouldn’t.
Next I tried to find the best path for the wires to go, without making new holes or pinching the wires.
Whoops, the included wire to go from the controller to the motherboard is too short for where I am placing the controller. Time to make a mod to the mod! I had to very carefully take apart the JST SR04 jack and swap it with a longer wire. Good thing they provided all the needed parts. Note the correct pin layout to make sure its recognized (the included cable had the pinout backwards!)
Next, the bluetooth adapter. The kit also had two JST SR05 to USB connector. After removing the plastic housing to my already small bluetooth adapter, I could easily fit it inside the case. Now I have all 3 external USB adapters free again, and nothing to forget or lose. Now I can tether to my cell and still look cool!
A Better view of the touchscreen controller.
Fitting the touchscreen. This was a PITA to get correctly centered, but I got it eventually.
After putting everything back togeather, I had to first turn the “camera” port on in the BIOS, then Fedora recognized the controller and USB devices on boot!
Now, even though I am running Fedora 11, which has support for just about every product under the sun, I still had to install drivers for the controllers, which was easier done then said.
First, I had to make a generic Xorg config, as Fedora does not make one now (its made on the fly)
[root@localhost ~]# Xorg -configure :1
~~ some output from Xorg ~~
Your xorg.conf file is /root/xorg.conf.new
To test the server, run 'X -config /root/xorg.conf.new'
[root@localhost ~]# mv xorg.conf.new /etc/X11/xorg.conf
Second I had to download and install the latest (2.06.2905 [beta]) drivers from the website [Local Copy of Drivers].
Then extract, and run the setup utility:
[root@localhost ~]# cd /tmp/
[root@localhost tmp]# tar xzvf ~drdelaney/Download/eGalaxTouch-2.06.2905-32b-k26.tar.gz
eGalaxTouch32/
eGalaxTouch32/readme
eGalaxTouch32/Guide/
eGalaxTouch32/Guide/How to rebuild kernel.pdf
eGalaxTouch32/Guide/How to build module.pdf
eGalaxTouch32/Guide/Driver Guide.pdf
eGalaxTouch32/eGalaxTouch.tar.gz
eGalaxTouch32/eula.pdf
eGalaxTouch32/setup.sh
[root@localhost tmp]# cd eGalaxTouch32/
[root@localhost eGalaxTouch32]# sh ./setup.sh
(*) Linux driver installer for eGalax Touch controller
(I) Check user permission: root, you are the supervisor.
(I) Begin to setup the eGalax Touch driver.
(I) Found and removed previous eGalax Touch driver.
(I) Extract eGalax Touch driver archive to /usr/local/eGalaxTouch32.
(I) Create eGalaxTouch utility shortcut in /usr/bin.
(I) Create TKCal tool shortcut in /usr/bin.
(I) Check X window version: 1.6.x
(I) Copy X module: x16/egalax_drv.so to /usr/lib/xorg/modules/input.
(Q) Which interface controller do you use?
(I) [1] RS232 [2] PS/2 [3] USB : 3
(I) Using interface: USB
(I) Found a HID compliant touch controller.
(I) Found X configuration file: /etc/X11/xorg.conf.
(I) Removed touch configuration from /etc/X11/xorg.conf.
(I) Add touch configuration into /etc/X11/xorg.conf.
(I) Please reboot the system for some changes to take effect.
(I) After booting, type "eGalaxTouch" to do calibration.
After rebooting, running eGalaxTouch, and calibrating, I had full touchscreen support!
So I am working on a personal project, and decided to rename the file. Now, I know from experiance that you cannot rename a file in cvs, and keep its commit history, but I decided to see if someone found a way. Well, someone did, partially… http://www.eyrie.org/~eagle/notes/cvs/renaming-files.html
He shows the way I used to do it, mv local file, cvs delete old file, cvs add new file, commit changes. – This deletes the cvs commit history
He also mentions about modifying the raw RCS file and renaming that, but apparently, cvs doesnt like that since cvs itself isnt aware of any changes.
So I tried a mixture of them, heres my process:
Find the raw RCS file: cat CVS/Root CVS/Repository – in my case, /cvs/projects
Copy that file somewhere: cp /cvs/projects/currentfile.sh,v /tmp
Rename the file in the current checked out sources: mv currentfile.sh newfile.sh
So I thought it was time to add something useful again to my blog.
Working with something for work, I had to configure a FC4 box with multiple IPs on different subnets, binding them to a sub nterface (eth0:1, eth0:2 and so on)
When we first got everythng on, only the primary IP address were working (bound to eth0 and eth1). All other interfaces were resolving to the physical ESXi servers MAC address on the switch, which is no good. After looking around, I found out there wasn’t support for this, everyone was saying to configure a Brige, or NAT everything through the local machine, which would NOT work out in our situation.
So after thinking a bit, I remembered the other issue we had with older OpenBSD 3.8 machines and the native VIC driver which was making the machines randomly crash reporting an unsupported mode. Well the resolution for that was to shut down the guest, and add in ethernet0.VirtualDev = “e1000″ and ethernet1.VirtualDev = “e1000″ to the guest-name.vmx file. So I figured I would try this on the Fc4 machine too, figuring I couldn’t lose anything. Well, I didn’t lose anything, but I gained a working ssystem, with sub-interfaces!
So for all of those out there with weird networing issues on an ESXi (ESX as well) guests, try changing the network emulation from built-in VIC to intel e1000!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-(+) s:+ a- C++ UBL++++ P+>++ L++(+++) E--- W++ N o K- w O M V-- PS
PE Y+ PGP t 5 X+ R tv b(-) DI D G e+ h+ r-- y+
------END GEEK CODE BLOCK------