LinuxMCE - User contributions [en]

GPT

2011-11-05T01:09:06Z

Tekoholic:

{| align="right"
| __TOC__
|}
[[Category:Tutorials]]
If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.

--forgive me, but this is no longer accurate. I've got some pretty old gear around here, and NOT ONE of my systems has any trouble booting to GPT (as opposed to "GTP") mbr... --tekoholic

== Creating Partitions ==
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.
parted /dev/sda

The next commands should be typed int the parted shell.

WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).
(parted) mklabel gpt <-- This one creates a empty partition table on the disk

(parted) print <-- List some information about the current partition table, size of the disc

(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location

(parted) quit <-- Exit the parted shell

After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:
partprobe /dev/sda
== Formating the Partitions ==
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:
mkfs.ext3 /dev/sda1
== Resize Partition Table ==
If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.
# parted /dev/sda

(parted) print
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all
of the space (an extra 1953103872 blocks) or continue with the current setting?
Fix/Ignore? F
== Resize Existing Partitions ==
'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Until this bugs get fixed the next instruction are here just for information purpose.</span>
Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.

For example, let's take a 5000GB drive that has a 4000GB ext3 partition on it.
(parted) print
Model: AMCC 9650SE-16M DISK (scsi)
Disk /dev/sda: 5000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 17.4kB 4000GB 4000GB ext3 primary

To resize that partition, you need to use the ''resize'' parted command which has the fallowing syntax :
resize <partition_no> <new_start> <new_end>

To transform the partition from our example from 4000GB to 5000GB :
(parted) resize 1 0GB 5000GB

Bluetooth Proximity Setup

2011-11-05T00:59:25Z

Tekoholic:

{{Versioninfo}}
[[Category: Tutorials| ]]
[[Category: Bluetooth]]

'''I will clean this up and make it a full how-to later, just wanted to get this out there for now, feel free to beat me to the clean-up'''

*Using the bluetooth signal from a phone or some other device that you routinely carry in your pocket, the computer can automatically detect when you enter and leave the room (or at least the general vicinity)
*This method isn't so good when multiple Media Directors are being used, because bluetooth can only connect and monitor signal strength between one pair at a time
#Upon insertion of the bluetooth dongle, MCE should automatically recognize it and set bluetooth up for you
#After this, it may ask to reload, regen, etc
#If any bluetooth devices are in the area and visible, MCE will ask you if you want to use them, etc
#My phone is not supported as a mobile orbiter, so I clicked "do not use"
#Once all that is done and the dongle is setup, go to the KDE desktop
#Web Admin > Wizard > Devices > Security
#Click "Add Device"
#Under Device Template, select "Generic Sensor" and click "Pick Device Template"
#Select "Bedroom(Master)" from the drop down menu on the left
#Click Update at the bottom
#Make note of the device number at the top left corner
#In terminal run 'sudo apt-get install blueproximity'
#Run BlueProximity by going to K menu > Applications > Utilities > BlueProximity
#Right click the BlueProximity icon (bluetooth icon with key) and click preferences
#Put your bluetooth phone or device in discoverable/visible mode (See device's documentation)
#Click on "Scan for Devices"
#When it has finished scanning, click the desired device and then "Use Selected Device"
#A pairing request should then appear on the phone, accept it and enter a passkey
#Enter that same pass key on the computer when it asks
#If your phone gives the option, choose "Always Connect" (This will automatically connect the phone and media center when they are in range of each other)
#The sliders in the "Proximity Details" tab can be adjusted to the proper settings for being outside the room (Locking) and inside the room (Unlocking)...this takes some trial and error to get the right setting, but be patient and it will work
#In the "Locking" tab, replace the "Locking command" with "/usr/pluto/bin/MessageSend localhost '''62''' -1000 2 9 25 0" replacing 62 with the device code of the generic sensor you created
#Replace the "Unlocking command" with "/usr/pluto/bin/MessageSend localhost '''62''' -1000 2 9 25 1" again replacing 62 with the device code of the generic sensor
#Erase the "Proximity Command"
#The generic sensor will now be tripped when the phone is in range, and untripped when it is out of range
#Web Admin > Events Handler > Respond to Events
#Set the description to "Bluetooth enters room"
#Choose "A sensor is Tripped" in the drop down menu
#Click Add
#Set what device to "= Generic Sensor"
#Set trigger state to "tripped = 1"
#Click update
#Choose "Lighting Wizard" from the drop down and select the lights you would like to turn on/off/set level/leave unchanged when you enter the room
#Repeat the last 8 steps, with the description "Bluetooth leaves room" and the trigger state "tripped = 0" for the lights you want to turn on/off, etc when you leave the room
#After a reload router/orbiter regen...and possibly a full reboot...you should have proximity set up for you to leave the room and come back in
#Fine tune the sliders in BlueProximity to avoid lights turning off unintentionally

Apparently, blueproximity is not supported by developer since 2008, and in (K)Ubuntu 10.04 has lost the basis for it's capabilities. Lucid is not able to determine signal strength for bluetooth, by way of past or presently known methods, unfortunately. With 10.04, unfortunately, you're either connected or not, by all available info.
--tekoholic, November 04, 2011

Bluetooth Proximity Setup

2011-11-05T00:57:04Z

Tekoholic: Broken in 1004, due to bluetooth code rewrite (or regression, as the case may be).