I don't want to install another hybrid System, and I don't want to
boot my Media Director Diskless over the Network (cause it needs up to 15 minutes to get the system).
How can I install a Media Director and tell it which Core to use ?
(How can I do this in 1.0 and in 1.1 beta ?)
Thanks for any help in advance!
Right now as I understand it, the only way to have a media director is to have it net boot from the core. I'm curious about the 15 minutes you're talking about. Originally, the core has to create an O/S image for the MD, but once that happens, later boots are very quick. The image loads over the network in less than a minute (considerably less in my case).
Linux MCE beta 2 supports DIsked MD's.
So you install Kubuntu on a PC, connect it to the Internal LAN of the CORE, install the mce-installer and when asked select install as Media DIrector
Quote from: Cj_MaN on June 14, 2007, 11:08:25 PM
Linux MCE beta 2 supports DIsked MD's.
So you install Kubuntu on a PC, connect it to the Internal LAN of the CORE, install the mce-installer and when asked select install as Media DIrector
This is not possible with 1.1. I only can Install a Core or a hybrid, but not a MD only.
What else could we do ?
Thanks for any help in advance.
I'm still a little confused as to why it takes 15 minutes for your MD to boot. What does it get stuck on? Do you see the O/S start booting? I'm wondering if you have a problem that's causing your long boot times.
I have to correct - It took so much time to boot because the orbiter was not finished...
But - currently I have problems with my graphic adapter: I got it running perfectly in Ubuntu 7.04 only - but when booting over PXE the Boot Image in 1.1 does not provide the correct settings :-(
So the issue is still there: What do we have to to, to get a media director running on top of a fully functional KUbuntu 7.04.
What's the problem with your adapter? Which adapter is it?
Quote from: PeteK on June 14, 2007, 09:52:47 PM
Right now as I understand it, the only way to have a media director is to have it net boot from the core. I'm curious about the 15 minutes you're talking about. Originally, the core has to create an O/S image for the MD, but once that happens, later boots are very quick. The image loads over the network in less than a minute (considerably less in my case).
With lmce1.1b2 all you need to do to create a non pxe booted MD (ie one that does not boot from the Core you have already installed) is to install the installer on the Kubuntu 7.04 machine you want to create as an MD and then run the installer. Make sure that this machine is on the same net (and has an IP issued by the Cores dhcp) as the core and the installer will recognise that you already have an existing working Core and will offer you the option to install as a standalone MD... just say yes and your on your way! We have several MD setup this way and they work great (in fact the Kubuntu machine i am using to write this is such a machine)
Hope this is of some help
Andrew
I also want to create an MD that isn't diskless. I tried using the quick install DVD and it automatically installs it as a core. Do I need to use the install CDs instead?
I installed using the "three disk method" Kubuntu/LMCE1/LMCE2
And it told me that "It seems you allready have core, you don't need two cores, do you wish to install an MD only?" (or something similar)
So I did it that way, and it works ok.
(It woun't work if the core is down though)
Good possibility! Plutohome doesn't offer such functionality.
Just a quick note to add here :-
The first time I tried this type of install of the MD, I got the right messages etc about the core being present etc etc, but the install did not work correctly. I discovered a device under the actual core (within Pluto admin - device tree) called DCEROUTER which was my previous attempt at getting this machine added. I deleted this device (Important: after checking the IP address and mac address matched my new MD) and reloaded the router.
I went back to the new MD and tried again - All good now, currently installing as I type ..... sweet!
HTH anyone who is having troubles.
Quote from: ozmule on October 02, 2007, 01:31:02 PM
Just a quick note to add here :-
The first time I tried this type of install of the MD, I got the right messages etc about the core being present etc etc, but the install did not work correctly. I discovered a device under the actual core (within Pluto admin - device tree) called DCEROUTER which was my previous attempt at getting this machine added. I deleted this device (Important: after checking the IP address and mac address matched my new MD) and reloaded the router.
I went back to the new MD and tried again - All good now, currently installing as I type ..... sweet!
HTH anyone who is having troubles.
You deleted the DCERouter device to fix a problem? That really surprises me, are you sure?
Any core that is created ID's itself as a DCERouter even to the main core. Media directors are all MoonXX (where XX is the device number). I have built stand alone boxes by using a single NIC, disabling the DHCP server, setting the primary NIC to DHCP and turning off the firewall. It works quite well as a stand alone media device. And accesses the content that Myth wants to announce from the core. I think I can add the rest of the content from the core but it hasn't been necessary yet. It won't control the core in this form.
Quote from: Zaerc on October 02, 2007, 01:36:37 PMYou deleted the DCERouter device to fix a problem? That really surprises me, are you sure?
Absolutely sure! This was a device under the Core/Hybrid in the tree view.
HTH
Quote from: ozmule on October 04, 2007, 10:05:06 PM
Quote from: Zaerc on October 02, 2007, 01:36:37 PMYou deleted the DCERouter device to fix a problem? That really surprises me, are you sure?
Absolutely sure! This was a device under the Core/Hybrid in the tree view.
HTH
Yeah, but it's also the heart of a LMCE system. Without that device none of the other components can communicate, hence I am a little puzzled. Did you have more then one of those?