Ok Verizon was just pissing me off by pushing the OTA updates to my phone. After dealing with "Install later" for 3 weeks, I finally managed to disable OTA updates using a trick I found on a forum.
First, make sure you have adb installed & that it can pick up your device. Next, adb shell into your device & type the following commands:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
sync
reboot
This one really drove me insane. I recently discovered JavaScript MooTools library & it's UI component, MochaUI. MochaUI provides a powerful & easy-to-use library for developing rich internet applications (RIAs).
My issue began after finding that the version on the website was highly out of date. I was looking to use OmniGrid alongside MochaUI, but the latest released version is mochaui-0.9.7.
After cloning the Git, I discovered that the new Demo contained far more features, and was much better laid out than the 0.9.7 release. I also found that the JavaScript files were provided as "source" to MochaUI. This confused the hell out of me, as how would I "build" JS files?! Three hours later after scouring Google & the terrible documentation on github, I managed to find this blog post which pointed me in the right direction.
It turns out each MooTools component contains a "package.yml" YAML file which is fed to a PHP script called "Packager." Package simply concatenates the source files listed in the manifest (package.yml) together. So much for "building" the JS :/.
Here's the complete steps to produce a "mochaui.js" file from github.
First, clone the MochaUI codebase & cd to the new directory:
Next, I had to modify the "package.yml" file to point to the correct sources directory. The original was incorrect, containing the wrong path & core files. Note: You must have the source files listed in this exact order, lest nothing will work properly.
My new "package.yml" file looked like so:
name: "MochaUI"
version: "0.9.8-dev"
exports: "mochaui.js"
web: "[mochaui.com](http://mochaui.com/)"
description: "MochaUI, A web applications user interface library"
Next, I proceded the use the same steps above to clone Packager from: git://github.com/kamicane/packager.
Once cd'ed into my packager directory, I ensured that I had PHP installed. That's an entirely different subject, but if you have access to the "php" command, enter the PHP interactive shell with the command "php -a"
[user@box:~/Desktop/test/mochaui/packager]$ php -a
Interactive shell
Once in the interactive shell, we need to include the "packager.php" file with the require_once() method. Once PHP knows about the Packager class, we can create a new instance.
As per the git's documentation (https://github.com/kamicane/packager), we can see that the constructor to the Packager instance is simply the path to the "package.yml" manifest file. In my case, this is simply the parent directory. Next, the write_from_files() method takes two parameters, but we really only need to know about the first. This is the output file name. Considering we are building the "mochaui.js" file, that's what the parameter will be.
After exiting the PHP shell, your Packager should now contain the fully "built" mochaui.js file.
Hopefully that'll save you some time & research :).
A client recently struggled when his XP workstation's left pane disappeared. This pane contains commons tasks such as emailing files.
A simple registry modficiaton was needed to remediate the issue:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"WebView"=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"ClassicShell"=dword:00000000
After applying the fix, I killed the "explorer.exe" process, then re-opened it. The pane was now visible.
Tired of trying to use compiz to have wallpaper span both screens, only to find your desktop icons disappear?
A few months ago I embarked on a relentless search through mountains of RGBA patches, custom versions of nautilus, and failed attempts at allowing desktop icons to pierce through compiz's iron curtain.
Finally created a decent method of having wallpaper span dual monitors in Gnome by overriding Gnome's "Spanned" desktop setting (I don't think it works right anyway) with a "Zoomed" dual monitor setting. I first tried this by scaling the image directly, but it looked like crap so I figure Zoom would be better to use. The result is not perfect, but definitely better than waiting 15 years for the Gnome team to come up with a plausible solution.
The steps I took were for Arch Linux, but you can apply them equally well to any distribution, as long as you know how to make packages from source.
After reading through this bug, I realized I should be modifying the desktop settings directly.
I checked my Gnome version through pacman, and proceeded to download the PKGBUILD straight from the Arch SVN. After receiving the source code, I ran "makepkg" once to ensure the source would compile properly, then proceeded to comment out the following lines in the PKGBUILD file:
To ensure that the source code would not be downloaded again & overwrite my modifications.
Next, I proceeded to open the "src/gnome-desktop-2.32.0/libgnome-desktop/gnome-bg.c" file, and commented out the following line, simply copying the Gnome "Zoom" option's code to the "Span" section of the case statement:
switch (placement) {
case GNOME_BG_PLACEMENT_SPANNED: // new = pixbuf_scale_to_fit (pixbuf, width, height); new = pixbuf_scale_to_min (pixbuf, width, height);
break;
case GNOME_BG_PLACEMENT_ZOOMED:
new = pixbuf_scale_to_min (pixbuf, width, height);
break;
case GNOME_BG_PLACEMENT_FILL_SCREEN:
new = gdk_pixbuf_scale_simple (pixbuf, width, height,
GDK_INTERP_BILINEAR);
break;
case GNOME_BG_PLACEMENT_SCALED:
new = pixbuf_scale_to_fit (pixbuf, width, height);
break;
case GNOME_BG_PLACEMENT_CENTERED:
case GNOME_BG_PLACEMENT_TILED:
default:
new = pixbuf_clip_to_fit (pixbuf, width, height);
break;
}
Finally, in the next section continaing the "GNOME_BG_PLACEMENT_SPANNED" (around 20 lines down from the previous section), I made the following modification to the code--commenting out what is commented in blue, and replaced with the code in red:
I recently got back into trying to teach myself C++, mostly through YouTube tutorials (this guy's are pretty good). I only went to IRC for an answer at one point, but would like to share something I found & wasn't able to Google on.
Everyone should know how to use pointers when working with C++.. say we had:
#include using namespace std;
int main()
{
int num = 5;
int *pnum = #
cout<<"integer num (@"<<<") = "<<*pnum;
return 0;
}
Then we can see that integer num is set equal to five, and integer pointer pnum is set to the address of num. Normally, in C++, the "&" operator refers to the address of the object the operator is being applied to.
In the case of passing values to function by reference, I was quite confused when I found that we do not in fact need to dereference the reference passed as an argument. For example:
#include
using namespace std;
void increment_variable(int & x)
{
x++;
return;
}
int main()
{
int num = 5;
increment_variable(num);
cout<<"integer num (@"<<&num<<") = "<<
return 0;
}
In the increment_variable(int & x) function, we would think that to increment the value of the x variable, we would need to dereference the address of the x variable, which has been passed as a parameter. As shown by the code, this is not in fact the case!
In reality, the "&" operator when used with pointers is a completely different operator than the "&" used when passing values to functions by reference.
As a network tech, I should always follow the golden rule of backup up data. I recently attempted resizing a partition (after neglecting this pinnacle of IT) & completed destroyed a PHP web application I had been working on.
The PHP web application was stored in a VM on the host's ext4 partition, and I had managed to destroy both the superblock & journal of the host's filesystem. After an unsuccessful attempt to restore the superblock from a backup on the drive, I figured the FS to be toast, but couldn't accept that the data had been completely lost.
What I really should've done was taken a DD image from the get-go with the following command:
After a bit of research and IRC chat, I was directed toward the following page: http://wiki.yak.net/592. The script seemed perfect for what I had needed to do. I knew the destroyed partition had only been 0.1% non-contiguous, so my hope was to completely recover the virtual hard disk image, or at least a repairable copy.
To begin, I created a test, dynamically expanding VDI file & opened it within a hex editor:
I could now see that each VDI file began with the string "<<< Sun Virtualbox Disk Image >>>"--the idea was to copy a large amount of data past where the script managed to locate things string, and to chop off the residual data with a hex editor.
I proceeded to test the procedure by placing the small test VDI file on an ext4 drive, searching for the data by reading the drive byte by byte, and copying only a small amount of data (~1mb) past the point where the magic string was found. The test was successful, though I still doubted I'd be able to recover a usable VDI file.
After a bit of modification to the script posted above (http://wiki.yak.net/592), I was able to successfully pick up around 10 VDI files off my dead drive (arbitrarily sized to 4GB past the magic string). After a bit of searching through these recovered VDI files, I found the exact file I was looking for. Unfortunately, my suspicions were confirmed when GRUB was found, but damaged beyond repair.
From here, I scrapped the whole idea of recovering the VDI and went directly for the plain text data off the drive itself.
To search through the drive, I ran the command:
$ grep -ab "php" /dev/sda4 > grepped
As I knew I was searching for plain text files that began with "php"--the search worked flawlessly. The "-b" option on grep, also records the decimal memory address where each instance of the string was found.
When the search completed, I had a list of the location of every instance of the "php" tag on the drive. This was a massive amount of data to sift through, but I managed to find the location (or at least get close to the location) of the important data I needed, by refining the search with the code's filename; for example:
Basically, we can see that a reference to the filename "MY_Controller.php" & a memory address of 391021232450 (decimal). After heading over to the offset through wxHexEditor, I can see quite clearly that my PHP code is in fact intact:
And it's complete with formatting & indentation :). From here, I've simply copied & pasted out each file as I found them, though some were not quite as straightforward.
It'll take a lot of hard work & determination to get your files back, so you need to decide whether it's worth it.
Also try out PhotoRec & foremost if you need to recover stuff that isn't plain text.
(I may post a condensed version of this document with only a short summarization of plain text data recovery techniques if anyone actually reads this)
When booting a VM recently, I received the error message below regarding I/O writecaching & virtual hard disk corruption:
After Googling for a bit, I found that the first thing to check with this error is whether I/O write caching is enabled on the VM. In my case, it was.
Next, a lot of the posts I was reading were stating the corruption was occuring on "ext4" partitions. I assumed that the write caching was a filesystem option. I had heard of the disk write cache when working on Windows servers, but never really knew the specifics.
After a bit more research, I found disk write-caching was actually a drive option that could be set with the hdparm command. It will improve performance by 10-20%, but can also cause system instability.
To enable write-caching on the drive, I ran command:
If you're getting frustrated by Outlook 2007 clients receiving error 0x80070422 when trying to Send/Receive the Offline Address Book, the first thing to check is your Exchange 2007 service URL's.
The quickest way to test this from the client end would be to hold CTRL & right click your Outlook 2007 Icon. Choose the option "Test E-mail Autoconfiguration..."
This will open up a new window (see below). In this window, uncheck the options "Use Guessmart" & "Secure Guessmart Authentication." Enter your password & hit "Test."
If your AutoConfiguration test completes successfully, then you're probably wondering why you're still receiving error 0x80070422. If your email AutoConfiguration test does not complete successfully, please verify your Exchange 2007 Web Service URL's as per this article.
Once you resolve any issues with email AutoConfiguration, many Outlook 2007 issues will also follow! A good example would be when you know that your server certificate is valid, yet you're still receiving a security warning similar to:
Check those service URL's!
Now, the next step to remediating your 0x80070422 error (which is a CLIENT SIDE ERROR), enable the BITS service on the client PC.
Just had an issue where I could not mount my USB drive at boot time I was getting an error along the lines of UUID=blah not found...I previously had performed the standard "sudo blkid" and received the following output:
Noting the UUID of my external USB drive (Elements), I added the following line into my fstab file:
UUID=7da36762-56c3-471d-bfa1-5b4895bfa0d7 /media/Elements auto defaults 0 0
Everything went dandy with a "mount -a" yet at the next reboot, I received an error stating that the device with the UUID 7da..could not be found. A bit of research lead me to the solution... Including "usb" before "filesystems" in the hooks section of your /etc/mkinitcpio.conf file:
HOOKS="base udev autodetect pata scsi sata usb filesystems v86d"
Regenerate your mkinitcpio file with:
sudo mkinitcpio -g kernel26.img
Then be sure to make a backup of your old /boot/kernel26.img
sudo mv /boot/kernel26.img /boot/kernel26.img.bak
Finally, copy your new kernel26.img to /boot.
cp kernel26.img /boot/kernel26.img
Now reboot and your external drive should be mounted automatically with no issues.
Completely unrelated to the song, but quite a dope ass song:
1773 - Broken Star
Broken star,
I see you from afar,
With your upper torso pressed up against the passenger side of a car,
Attention directed towards some cat,
Pullin' over in the Cadalliac,
Cause he noticed your back was fat,
But the fact is your attempts are to supplement what you lack,
Trapped into believing what some stranger had promised you,
Mainpulating, stating, that this ain't nothing that you gotta do,
Conning you before you know he turns to you and speak,
Don't worry it's just gonna be,
Herpes you and me,
Now disease and the sea symoblize your promiscuity,
I knew a similar star that was already broken,
I'm speakin' on something that you already knowing,
Traveling all roads,
That long have been chosen by a man who control,
Her mind and her soul,
Always treated her cold, and always needed to know, where she would be,
And what time she was there 'til,
If he thought she was lyin',
He would give her a black bruise,
As a youngin',
She was always a tad lewd,
The story of her life,
Struggle to survive but barely staying alive,
Wanting to end the strife,
[Chorus]
Broken star,
Can't you see that you are falling oh so fast?
This won't last
She was a broken star and couldn't travel far,
Broken star,
Can't you see that you are falling oh so fast?
This won't last,
She was a broken star and couldn't travel far,
This broken star was constantly filled with pain,
No one was able to see, the tears in her name,
She was a slave, to the fear, that had claimed her life for so long what else can go wrong,
She could hardly hold on,
She said his grip was so strong,
And she couldn't break free,
And she get loose,
His hands, tied around, her neck like a noose,
She was tired of it, and wanted something new but didn't know where to start,
Alone in her heart,
Wanting to get far was the state of this star,
Mentally damaged with emotions to manage,
Physically famished to the point your lists have anything that's handed,
Branded by beasts who won't deny,
What they demanded and that seed that's implanted suddenly forced to vanish,
Created by a stranger and we didn't plant it,
It's the thought that led you to your decision,
Cause you figured it'd be better of dead than with an infected one to livin',
Given' the circumstances,
You justify your actions,
By saying you were given a corner and forced by back in,
But really it was what you chose that made this happen,
[Chorus]
To get ahead you feel you're doing what you have to do,
But simultaneously spreading what was passed to you,
Back when you were half developing, initiated,
Enabled to count all the times that you been degraded,
Now you feel you kid your soul and you wished you saved it,
Jaded from being so misguided and the world divided,
Thought this was the plan for life but now you wanna revise it,
It be wise you changed before you're old and scarred,
And grow so far from being who you know you are,
Cause you use to shine bright now you're a broken star,
She finally gathered the strength to leave this man,
No longer, will her face come in contact with his hand,
She's starting to realize that she seems to understand,
What it is she has done,
And what she's gotta do,
Now she sees the sun and the sky so blue,
And for the first time in her life, she feels real peace,
Left another man in her life, initials J.C.,
He heard her cry out when she yelled "save me!"
He came to her rescue and said I will mend you,
No longer broken star, my love now protects you,
[Chorus]
You're a star, you're a star,
So let your light shine,
Cause the nigga's see the light and the light so bright,
Let your light shine,
Cause the nigga's see the light and the light so bright.
Had some trouble with something I'd had earlier trouble with in the past. When using the locate command (even after running updatedb), I was unable to search my removable USB drives.
The solution was to modify the /etc/updatedb.conf file, and remove /media from the prune path:
So I recently set up a VirtualBox VM on my Windows 7 machine so I could access my XFS hard disk through a network share.
Being there's no way to hide a VirualBox VM by default (even by running in headless mode), I went ahead & wrote a quick C# program to hide running windows.
First of all, I created a .bat file to run my VM headless...the contents are as follows:
cd "C:\Program Files\Sun\VirtualBox"
VBoxHeadless.exe -s Ubuntu
