I had a desire to enable compression after the fact on some shares. Synology (As of DSM 6.0) doesn’t have the facility to modify the compression settings of a folder after the initial creation – and perusing the forum, it seems you can’t enable compression at all on the /homes location.
Much discussion orbits the topic of chattr, how it isn’t installed and how to go about installing it. I have a way to do it without installing anything! btrfs-progs is already installed 😀
SSH into the device, and issue the command (as root)
btrfs property set /volume1/homes compression lzo
The btrfs command gives you plenty of other options to explore – perhaps best as a non-root user. Now to find a built-in for disabling Copy of Write.
I found myself in a situation: Securom error 1000. Or, “we don’t like you because you don’t fit our corporate model of the ideal consumer.”
Disclaimer: This is a lesson in overcoming corrupt read-only media.
I wanted to install a piece of software that didn’t like my particular set of software installed. More specifically, I was having trouble installing Oblivion GOTY because the Securom protection doesn’t like that I run Windows virtually within OSX with Parallels. Or maybe it’s the disc emulator software installation. However the case, this post is how I circumvented that difficulty using UNIX WIZARDRY and a patched setup file. Users win every time.
So you have a cisco device that is password protected, perhaps it is a mission critical core device and you lost the password. It doesn’t matter why, but maybe when you recover it, take note of it this time.
So what I present here is a method for actually recovering the MD5 hashed “Enable” or user passwords through a dictionary attack (and physical access). Continue reading →
Alright… I did it. I put the Vista disc in and did the install thing. It took a long time. The first thing I noticed: Nothing. No choices! No customization other than timezone. There wasn’t any obvious click here to fix buttons. Yes, I am alluding to the fact that Vista is broken upon installation.
Okay, I’m extremely critical and biased… but I’ll try to be fair.
First, it doesn’t install right — It wrote over my boot loader with some crap-encrusted near-sighted Windows-Only thing. It’s useless, how do I access Linux with this? So I needed to boot with a forensic Linux disk and reconstruct a less-than-useless bootloader: Grub