Monday, January 14, 2013

Using rsync to keep my media files current.

All,

I've been using rsync to keep my media folder current between my server and an external drive. The server is an ext4 partition and the remote drive is formatted as NTFS for compatibility reasons.

I've written a little bash script to make this fool proof. One option to sync to my media server and one option to sync to my desktop where the external drive gets mounted.

The media server is mounted via CIFS to my workstation as /storage/media/Movies

The external drive is mounted NTFS-3g as /external/Movies

#! /bin/bash
PS3='Please enter your choice: '
options=("Sync to Server" "Sync to Desktop"  "Quit")
select opt in "${options[@]}"
do
    case $opt in
        "Sync to Server")
            echo "you chose Sync to Server";
            rsync -rltDvu --modify-window=1 --progress /external/Movies/ /storage/media/Movies/;
            break;
            ;;
        "Sync to Desktop")
            echo "you chose Sync to Desktop";
            rsync -rltDvu --modify-window=1 --progress /storage/media/Movies/ /external/Movies/;
            break;
            ;;
        "Quit")
            break
            ;;
        *) echo invalid option;;
    esac
done


This script give me 2 options. 1 Syncs from the external drive to my server and 2 syncs from the server to the external drive.

I'm no bash wizard but if this helps you great!

Sunday, October 7, 2012

Samsung s3 Galaxy MTP file access with Slackware 14

I just got my hands on the new Saumsung s3 Galaxy and I love it. The only problem I had was that the device does not present itself as a standard USB thumb drive like the old Android devices do, rather you get to choose between MTP (Media Device) access and and PTP (Camera Device) neither of these seemed to work for me with a default install of Slackware 14.

gMTP to the rescue!!!


gMTP  will allow you to manage, upload and download files on the Galaxy s3's internal storage as well as the SD card.

I've created packages for Slackware 14 x86_64 that you can download below. You will need the scons, libmtp, mtpfs, and gMTP packages installed, then simply connect your phone via USB and run gmtp, you will then be given a drop down box to choose between the phones internal storage or the sdcard.

Kens slackware packages

12/25/12 UPDATE: Upgraded this package to version 1.3.4

you'll also need to add a udev rule under /lib/udev/rules.d/ called

51-android.rules

paste the following into the above file with your favorite editor:

 # adb protocol on Galaxy S3
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666"


Saturday, September 29, 2012

Slackware 14 has been released :-)



ftp://ftp.osuosl.org/pub/slackware/slackware64-current/ChangeLog.txt


Wed Sep 26 01:10:42 UTC 2012 Slackware 14.0 x86_64 stable is released! We're perfectionists here at Slackware, so this release has been a long time a-brewing. But we think you'll agree that it was worth the wait. Slackware 14.0 combines modern components, ease of use, and flexible configuration... our "KISS" philosophy demands it. The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware project by picking up a copy from store.slackware.com. We're taking pre-orders now, and offer a discount if you sign up for a subscription. Thanks to everyone who helped make this happen. The Slackware team, the upstream developers, and (of course) the awesome Slackware user community. Have fun! :-)

Saturday, August 25, 2012

Ghettonet.org is coming back!

About 6 months ago I let the website I hosted for 10+ years die due to lack of interest on my part. Ghettonet.org is coming back as this blog, once the DNS records are propagated this blog will be live at www.ghettonet.org.

Slackware 14 RC3 is out

From the latest changelog

ftp://ftp.osuosl.org/pub/slackware/slackware64-current/ChangeLog.txt

This is Slackware 14.0 release candidate 3, and is hopefully the last stop on our long road to a stable Slackware release soon. After hearing that the 3.4.x kernel series will have long term support, I tested 3.4.9 hoping that it would prove stable enough to use that as the release kernel, but there are problems with an oops in kernel/time/clocksource.c every few boots. Given that the 3.2.x series has been very stable, it seems prudent to stick with that for release, and 3.2.28 is going to be the release kernel. So, one more round of testing. Let me know if there are any problems. Thanks!