Difference between revisions of "Storage Devices"

From LinuxMCE
Jump to: navigation, search
(Background Info)
(Background Info)
Line 6: Line 6:
 
== Background Info ==
 
== Background Info ==
 
This bash scripts where created to configure / setup storage devices that can be used in pluto. Currently there are 2 device templates that can be configured by this scripts:
 
This bash scripts where created to configure / setup storage devices that can be used in pluto. Currently there are 2 device templates that can be configured by this scripts:
*Hard Drives / Generic Internal Driver (1790)
+
*'''Hard Drives / Generic Internal Driver (1790)'''
*Network Storage / HD-HG300LAN (1794)
+
*'''Network Storage / HD-HG300LAN (1794)'''
  
 
This device templates have some common device data:
 
This device templates have some common device data:
* ''PK_Users (3)'' : A list of integer values separated by comma. The numbers represent the id of the users who can use the storage device for storing private files on them. If the 0 value is there too, the storage device can also be used to store public files. If no value is entered, the default is considered 0 (public only). If the next device data (use pluto dir structure) is not set to 1, all the files will be accesible from one directory on the storage device, meaning that public / private files can be accesible by every user that can access that device.
+
* '''PK_Users (3)''' : A list of integer values separated by comma. The numbers represent the id of the users who can use the storage device for storing private files on them. If the 0 value is there too, the storage device can also be used to store public files. If no value is entered, the default is considered 0 (public only). If the next device data (use pluto dir structure) is not set to 1, all the files will be accesible from one directory on the storage device, meaning that public / private files can be accesible by every user that can access that device.
  
* ''Use Pluto Directory Structure (130)'' : This value can be 1 or 0, meaning that the information on theat devices will be stored using a pluto directory structure, identical to the one in /home directory. For every user there will be a separate directory to store it's private data and there will also be a /public directory in there. The default is set to 1 but if other/no value is entered will be considered 0.
+
* '''Use Pluto Directory Structure (130)''' : This value can be 1 or 0, meaning that the information on theat devices will be stored using a pluto directory structure, identical to the one in /home directory. For every user there will be a separate directory to store it's private data and there will also be a /public directory in there. The default is set to 1 but if other/no value is entered will be considered 0.
  
* ''Use Automatically (134)'' : A leftover ? Not used  
+
* '''Use Automatically (134)''' : A leftover ? Not used  
  
* ''Directories (153)'' : The media directories from the pluto directory structure that can be used on this device. Example by entering ''music, movies'' only the music and movies folders will be available from pluto. The value can be empty, meaning that all directories will be available.
+
* '''Directories (153)''' : The media directories from the pluto directory structure that can be used on this device. Example by entering ''music, movies'' only the music and movies folders will be available from pluto. The value can be empty, meaning that all directories will be available.
  
 
== File Details ==
 
== File Details ==

Revision as of 11:45, 17 April 2006

This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.
== General Info ==

Package: pluto-storage-devices

Directory: src/PlutoStorageDevices

Background Info

This bash scripts where created to configure / setup storage devices that can be used in pluto. Currently there are 2 device templates that can be configured by this scripts:

  • Hard Drives / Generic Internal Driver (1790)
  • Network Storage / HD-HG300LAN (1794)

This device templates have some common device data:

  • PK_Users (3) : A list of integer values separated by comma. The numbers represent the id of the users who can use the storage device for storing private files on them. If the 0 value is there too, the storage device can also be used to store public files. If no value is entered, the default is considered 0 (public only). If the next device data (use pluto dir structure) is not set to 1, all the files will be accesible from one directory on the storage device, meaning that public / private files can be accesible by every user that can access that device.
  • Use Pluto Directory Structure (130) : This value can be 1 or 0, meaning that the information on theat devices will be stored using a pluto directory structure, identical to the one in /home directory. For every user there will be a separate directory to store it's private data and there will also be a /public directory in there. The default is set to 1 but if other/no value is entered will be considered 0.
  • Use Automatically (134) : A leftover ? Not used
  • Directories (153) : The media directories from the pluto directory structure that can be used on this device. Example by entering music, movies only the music and movies folders will be available from pluto. The value can be empty, meaning that all directories will be available.

File Details

DownloadUpdates.sh
This script is runned by cron and downloads all the needed deb packages for doing an dist-upgrade on the Core and all of it's MDs. Also this script calls the NotifyUpdates.sh script to notify the user that the updates are available and he shoule reboot certain machine so they can be installed. This script runs only on the Core.
NotifyUpdates.sh
Notifies the user via orbiters that updates are available and that certain machines should do a reboot so they can update. It takes the PK_Device of the machine that needs to reboot as a parameter.
ApplyUpdates.sh
This is a startup script and is runned by the /etc/init.d/fastboot/rcS.d system initialization script before any of the pluto services get started. It checks if DownloadUpdates has downloaded all the needed packages and if so, it trigers a dist-updagrade. If a new kernel is one of the updated packages he also takes care of rebooting the system after all the updates are installed. This script is runned by Core and all the Diskless MDs.