- Details
My company's firewall enforces NTLMv2 proxy authentication, which kinda sucks for some Linux hosts since I can't pass that authentication directly on the command line. Maybe I'm dumb, but every command format I found didn't work. But this did work...
1. Install CNTLM package: apt-get install cntlm
2. Configure username/password in /etc/cntlm.conf.
3. Restart cntlm service: /etc/init.d/cntlm restart
4. Try this format: http_proxy='http://127.0.0.1:3128/' apt-get update
CNTLM does the authentication for you, so you can relax and think about more important things.
NOTES
* Enable remote hosts in cntlm.conf to allow other hosts to use this child proxy.
- Details
Make sure the partclone package is installed.
apt-get install partclone
Create an empty image file.
touch image-file.img
Restore the clonezilla files into the image file.
cat sda1.ext3.ptcl-img.gz.* | gzip -d -c | sudo partclone.restore -C -s - -O image-file.img
NOTES
* This is 3 commands on 1 line with pipes.
* Be sure to include the lone hyphen in the last command. That's not a typo!
Mount the image:
mount -o loop -t ext3 /folder-path/image-file.img /mnt
If you converted an NTFS partition, it probably won't mount. Try this...
Mount the image - NTFS:
ntfs-3g /folder-path/image-file.img /mnt
Special thanks to this very helpful forum thread: http://ubuntuforums.org/showthread.php?t=872832
- Details
My aged Netgear NAS was primed and ready for a relaxing retirement, so I pursued a befitting upgrade. I briefly considered an out-of-the-box NAS offering from Qnap or Synology, but reconsidered after considering the high price paired with the wimpy CPU & RAM specs. After considerable consideration I decided to build my own. An OS-less HP Microserver costs a fraction of what a Qnap NAS does, and this way I wouldn't be married to an over-priced, low-spec proprietary platform. But what OS to put on it? My hunt for the ultimate free open source NAS distro began.
Read more: The Hunt For the Ultimate Free Open Source NAS Distro
- Details
I hate it when a user's PC shuts down ungracefully, and they choose startup recovery at the next boot. The process (albeit "recommended") removes the PC from the AD domain...uggg... Therefore, I disable the startup recovery prompt altogether.
Run this at a command line or put it in a batch file:
bcdedit /set {default} recoveryenabled No
bcdedit /set {default} bootstatuspolicy ignoreallfailures
- Details
A corrupt WMI repository can mess up things like the Symantec management agent and its ability to deploy software. If you check properties of "WMI Control" in Computer Management (under Services & Applications), and it shows problems, then the PC likely has a WMI issue. Here's how to repair it.
I use powershell remoting to remotely run this, but it can be done at the PC's command line too. The command format below assumes powershell remoting.
Check the WMI repository.
1. Go to C:\Windows\system32\wbem
2. winmgmt /verifyrepository
If errors are found, try to repair the repository.
1. winmgmt /salvagerepository
Still not working? Then totally rebuild the repository.
1. Stop the Windows Management Instrumentation service.
2. Rename the C:\Windows\system32\wbem\repository folder to something like repository-old
3. Re-register relevant DLLs: cmd.exe /C "for /f %s in ('dir /b *.dll') do regsvr32 /s %s"
4. Re-register all the MOF files: cmd.exe /C "for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s"
5. Start the Windows Management Instrumentation service.