User:Posde

Links

Modeline generator for X.org [1]

PythonMO

The PythonMO is going to work on all Nokia Symbian S60v2 and S60v3 phones. S60v1 won't be supported, as one of the main objects (graphics.Image) is not supported on it. As Python is supported on a lot of other devices as well, it should be easy to move it to other devices as well. The PythonMO is a Bluetooth server talking to the BD service running on the LinuxMCE Media Director.

Flow

• All conversation work the same way. The server and the client talk using the following syntax.

4-byte long CommandID
4-byte long length of CommandText
0x00 delimited CommandText

• It provides a service names "Pluto"
• Upon connecting from a client, it sends out
  • A 4 byte version of a long BD_PC_REPORT_MY_VERSION
  • A 4 byte length definition of the BD_VERSION string
  • The BD_VERSION string, delimited with a NULL
• The client sends back
  • A 4 byte version of a long BD_CP_....*
  • A 4 byte length definition of the command text
  • The word OKAY ended with a NULL
• The server sends BD_PC_WHAT_DO_YOU_HAVE
• The client tells the server, what the server should display or send back.

Personal Goals for 0804

EPG and channel list on orbiter

The average user expects the electronic program guide to be viewable on the orbiter, and not only the on-screen orbiter. (Maemo Orbiter, Web Orbiter, Flash Orbiter [maybe Mobile Orbiter])

Working VDR

VDR integration as promised for 0710. LiveTV on all media directors, without an ugly hack.

Python Orbiter

As mentioned on top of this page, I want an orbiter realised in Python, especially for the Symbian S60 phones. But it can also be the basis, for a mobile orbiter runnning under Maemo.

LVM and RAID

Partition The First Disk

Currently, the installer does not work with previously created software RAID devices. Therefor, one of the three disks is used to create the boot device. DVD Install and Custom Partitions

Create a RAID 1

As the boot partition we will create a raid 0 array. First create partitions on two of the disks using fdisk

fdisk /dev/sda
n - new partition
1 - start of partition
+80000M - we take about 80GB of space. Enough for the initial / of LinuxMCE and a couple of MDs
t - change type of partition
fd - to a raid array
w - write changes to disk.

same for /dev/sdb.

Now we create the raid devices

mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1

If you receive an error, device /dev/md0 not found, make sure, the kernel module md is loaded, do

modprobe md

and try mdadm --create again.

Now, wait for the array creation to finish. Watch it with

cat /proc/mdstat

Now we have the initial device for LinuxMCE. Look at the wiki page [[2]] regarding custom partitioning, and create the three relevant partitions within the device /dev/md0 instead of /dev/sda and the relevant file and dir.

Now it is time to install LinuxMCE as outlined in the above wiki. When done, come back here.

Create a RAID-5 MD with LVM2 on top

LinuxMCE is installed and Sarah did his show and dance, and most of the stuff is configured. Now we will setup the array for the media. This array will be the foundation for an LVM2. Ontop of LVM2 will be an xfs file system. This will ensure ease in growing our media repository.

Install LVM2

aptitude install lvm2

takes of care of installing the needed programs

Create LVM2

A logical volume consists of physical volume groups and logical volume groups. First we mark our big RAID 5 array as a physical volume.

pvcreate /dev/md1

Next we need to create a volume group consisting of our array

vgcreate mediapv /dev/md1

The name 'mediagroup' is purely out of the blue. Name it pamela if you like. Next, after assigning the RAID array to the volume group, we add a logical volume group ontop of that volume group of physical volumes

lvcreate --name medialv --size 1700G mediapv

If you get an error during the above command, make sure the module dm_mod is loaded.

Format The LVM2 Partition

Now we have an LVM2 partition, that we can format. As we will put mostly large files ontop the drive, and use lots of disk space, we choose xfs

mkfs.xfs /dev/mediapv/medialv

If you get an error during the above command, saying command not found, install the xfsprogs using aptitude install Compared to formatting an ext2 or ext3 file system, the creation of the filesystem with xfs is very fast, as only a little bit of information is written to the disk.

Door bell and security camera

<simn_bx> TSCHAK, all... what does it mean in WIzard-Reaction to sensors, if i set for Generic analog camera under "disarmed" as "as Security??
<TSCHAK> simon_b, that only works if the camera is a child of the motion wrapper
<TSCHAK> simon_b, but if you do that, then motion will watch the camera and try to extrapolate motion, and send security events, that you can trigger off of.
<simon_bx> yes, the camera is a child of motion wrapper
<TSCHAK> okay, sooo
<TSCHAK> that means any time that camera detects motion, you can for example, trigger a security event
<simon_bx> hmmm, ok... trying to uderstand that...
<posde> simon_bx, could you do me a favor, once you understand everything, could you go and wiki everything?
* simon_b hat die Verbindung getrennt (Read error: 60 (Operation timed out))
<simon_bx> sure, no problem posde... i'm trying to add camera notivifacation on the orbiter, when doorbell button is triggered
<posde> simon_bx, I know.
<posde> and lots of people want to use that functionality eventually
<simon_bx> anyone succeeded?
<posde> TSCHAK :)
<posde> But I will eventually. 
<simon_bx> thru "Respond to events page"?
<TSCHAK> since I have a supported mobile orbiter
<_nano> posde, what do u recommend vdr 1.7 or 1.6 ?
<posde> _nano, I am using stable
<TSCHAK> all I did was drop a cam outside, and hook a door phone to an analog telephone adaptor, and set the ATA up to be extension 996
<TSCHAK> it shows it on my phone, but i also added a respond to events "someone rings doorbell" which triggers my door cam scenario under security.
<simon_bx> aha... ok, will play a little bit...
<TSCHAK> I used DCERouter Execute Command Group command, and gave it the scenario # of the panasonic IP camera scenario button
<simon_bx> well, that is already too deep for me... " DCERouter Execute Command Group command" (sorry for asking)
<TSCHAK> if you look at the list of commands
<TSCHAK> under DCERouter, there is a command, called execute command group
<TSCHAK> a command group, is the internal name for a scenario
<TSCHAK> it takes one parameter, the scenario number to run...
<TSCHAK> which you get by looking at a scenario, it will say, "Scenario #8: Sleep" etc...
* virsys hat die Verbindung getrennt (Read error: 110 (Connection timed out))
<TSCHAK> you get the # ,and put it in that fiel.
<TSCHAK> d.