The frontend_host_name is what you want to call your frontend, eg kitchenpc, or bedroom_pc, or Frontend1, whatever really.
I seem to recall not having to alter any settings as the script goes through, though I keep the suggested settings in my original setup ie Myth etc...

Once you've run the script, you need to boot the frontend. You need to set that frontend pc to boot from the network. The only way I could get it to do that was via a dhcp.

I forget exactly what the exact setting is called in the BIOS. (Originally I was hoping to get diskless frontend and Mythwelcome to work in concert, but couldn't get it up and running. I couldn't work out how to get the pc to look for a specific address but that might have just been a limitation of that particular computer.)

Once that has happened you rerun the script and your backend asks if you want to bind that address to that particular frontend.

It's pretty painless I seem to recall.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Ah...the wiki didn't mention that. Thanks, I'll hopefully get a chance to try this out tonight

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Thanks for the change owner info. I did however rerun the script that will setup DISKLESS FRONTEND and it worked correctly that time.

Wow this is great. I cannot wait to get my KnoppMyth box back up and running again. I just read through this, and had a question that maybe someone could answer.

I have setup several PXE enviroments at different places Iv worked, and would it be possible to configure the BE server to only respond to PXE requests?

In a PXE enviroment the server doing PXE does not have to be the same server providing DHCP. http://linux.duke.edu/~cegeddin/pxebooting.html

IMO this would be an ideal solution because it would not matter what IP addresses your using on the local network as long as the FE clients are in the same broadcast domain as the BE it should work fine.

Edit: Also it would not require anyone to go messing with their already working DHCP enviroment, and someone were using a router for DHCP that has limited configuration options this might be a better solution also.

JMO

In the dhcp.conf if you comment out the allow booting then it will only respond to those doing the pxe boot. I am doing this on my network because I also have another DHCP server on my network just for my other computers and this worked for me.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

Thanks sinspot1. I didnt see that mentioned anywhere in the posts so sorry if I missed it.

No you didn't miss it. Was just something I figured out for a problem I was having and no one has posted a question asking about it. So I had not posted it anywhere. I am glad it also work for you.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

Could the wiki be edited to include this information for future reference?

_________________
Girkers

I'm going to setup a diskless front end this weekend. Though, it never really clicked until now, with only a mobo, nic, and graphics card, I have no remote.

What would be the simplest (cost/ease of setup) route to add a remote to this system?

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Streamzap is a good USB remote.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

I have to ask: how does one setup a remote on a diskless FE? I'm a bit confused by this (my current test FE has no remote yet because I haven't been able to figure this part out...!).

I don't have a Streamzap, but I might buy one if it is easy to setup.

More specifically, what I'm looking for is a way to create multiple diskless FE that are uniform in spec/capabilities/features (i.e., they all use the same hardware, including the remote).

-sTv

_________________
R7.3 Backend
CPU: 1.8 GHz
RAM: 2Gb
Drives: 500Gb IDE; IDE DVD-RW
Mobo: eMachines
Tuners (Analog): PVR-250
Tuners (Digital): DCT-6200 Motorola Cable Box, HDHomeRun (OTA + cable)

that is a good idea to have all of your diskless FE with the same specs. The streamzap is a good and easy remote to use and is now part of the dragon 2.0 spec so when you install KM it will auto configure it or if you run the reconfigure remote script after the fact.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

This is where the wheels come off for me.

"Diskless FE" means there is no install to be done on the FE. So...the question remains:

How does one install a remote for a diskless FE?

My MBE has been configured with the silver remote that came with my PVR-250.

Is this where you mean "run the reconfigure remote script after the fact"?

LIke, run it on the MBE? Or run it on the diskless FE?

Sorry, my "stupid" gene is expressing itself big time on this one...


-sTv

_________________
R7.3 Backend
CPU: 1.8 GHz
RAM: 2Gb
Drives: 500Gb IDE; IDE DVD-RW
Mobo: eMachines
Tuners (Analog): PVR-250
Tuners (Digital): DCT-6200 Motorola Cable Box, HDHomeRun (OTA + cable)

if you are using the same remote on the MBE as your Diskless FE when you the run the disklessfe script it will pull over the settings and files. If you are going to use a different remote on the MBE and the diskless FE then after you have run the disklessfe script you can run the reconfigure remote script on the diskless fe and it will setup the remote for it.

Don't worry about it..... not a stupid question at all

_________________
Marty

Long live Myth and Knoppmyth!!!!!

Clearly, I'm not doing something right.

I ran:
knoppmyth_diskless_frontend.bash ChadsRoom

I left the ip settings alone (*.21-*.26)

It stopped my backend whoops, lost a recording...ah well.

Then set the bios on my other machine to LAN, and...nothing.

Not sure how to setup this fe to boot properly.

All I get is
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER

Which made me think it wasn't seeing the network...but, when I check my router, I see it appears to have grabbed an IP....my guess is something with my Router blocks it? I'm using a D-Link DI-524.

Edit: Maybe it isn't getting an IP...that must have been something else that grabbed that IP.

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb