To start off, thanks to cesman and the other folks who make knoppmyth possible, it's great.

I've been using it as a LiveCD so I can run MythTV frontend on my wife's laptop, trying to keep the peace by not installing Linux on her machine.

I'd like to be able to drop the CD in and have the frontend come up, without having to go through the configuration steps everytime. I understand that I'll need to remaster the CD in order to do this. The question I have is, how do I bypass the main menu and give it my "default" frontend, time-zone, DCHP? (I did find that the mythtv defaults are stored in mysql.txt)

I looked around in /etc/rcS.d and the S00knoppix-autoconfig file, it didn't look like the config script was getting lanuched from in there, although I did see mention of the knoppix.sh script that I wasn't able to find.

I did notice that if I'm at a shell and I logout 'exit' the script comes back up, I'm assuming that means it's tied into the userlogon/off event, I'm sure if I knew more about Linux that fact would tell me the right place to look, but I'm still relativly new to all this.

Thanks

Okay, I think I found what I was looking for.

It looks like things get started with /sbin/Start which then kicks off /usr/local/bin/KnoppMyth-main from there it fires off the other KnoppMyth-* scripts depending on choices made in the menu.

Once you figure out this process you should add a how-to at http://www.knoppmythwiki.org/. I am intrested in doing the same thing.

This topic may be of intrest. Details storing conifg on a USB drive.

http://mysettopbox.tv/phpBB2/viewtopic. ... ht=knoppix

I'm working this into a diskless front end via PXE network boot, I'll put up some documentation once I have the kinks ironed out.

Saving the config to a USB drive, cool idea, and probably a lot cleaner then what I ended up doing. Oh well.

I was using it last night to watch some LiveTV, just having some problems with the scripts getting me all the way into mythTV.

any luck with the remastering project? i'd be very curious to see how to go about it too!

_________________
ASUS P5N7A-VM, 2.5gHz E5200, 2GB crucial DDR2, pvr-250, hdhomerun, URC-8820 remote, Panasonic TH-42PZ80U, LinHES 6.01.00

I'm trying something similar. I have started to write up what I am doing on the Wiki (http://knoppmythwiki.org/index.php?page=DisklessFrontend). I am working it out as I go along, so may be off the track, but you have to start somewhere.

cool, looks like a good start, i'll give it a try and let you know how far i get thanks!

_________________
ASUS P5N7A-VM, 2.5gHz E5200, 2GB crucial DDR2, pvr-250, hdhomerun, URC-8820 remote, Panasonic TH-42PZ80U, LinHES 6.01.00

Greg,

I have been looking at this as well, but building a new image to give a "no-option" boot cd to a friend. I will dig out what I did and see if I can help out. I seem to remember that the home directories are actually "built" during boot. There is (somewhere !) a template for a hopme directory that is stamped out with the name of the user at install time, because Knoppmyth doesnt know you are going to call yourslf Mythtv . That may be your problem with /home/mythtv. As to the nvidia drivbers, I seem to remmber gettingh into a mess with those as well, so I will check it out, but am not that hopefull.

Perhaps this belongs in a new thread, thats fine if it needs to be moved... I'm trying to follow the diskless PXE boot wiki instructions, but i'm having a problem upon network boot. The knoppix screen comes up after i get an ip, but i get an cant NFSmount Knoppix error.

I cant seem to find more info on this error after googling around... I also notice when i stop or start the knoppix-terminalserver service i get a message that it cant stat several things and that i get a "disk full" 67% message that doesnt seem to correspond to my free disk space on any partition...

If anyone can point me in the right direction i'd appreciate it... Thanks!

_________________
ASUS P5N7A-VM, 2.5gHz E5200, 2GB crucial DDR2, pvr-250, hdhomerun, URC-8820 remote, Panasonic TH-42PZ80U, LinHES 6.01.00

If you're getting disk full messages even though you can see that there is free space on your partition, it probably means that you are out of inodes on that partition. Try df -i to view the inode status.

Greg Frost,

Did you ever get this working ? I was looking for a more flexible approach, so I have spent many a frustrating hour trying to get an NFSroot setup working.

The idea is that instead of producing a new image that you mount using -loop, you "simply" move the whole root filesystem from you frontend, once you have it just the way you want it, to the terminal server/backend. Then you boot over pxe, the kernel runns on th efrontend. but accesses the nfsroot on the backend, and roberts your mothers brother.

There are great how-to's around, but a lot of them seem to have been made obsolete for the latest kernels due to a change to the way the initrd image is built. (??). So I couldnt get a good initrd.gz image built that would contain the nic drivers I needed, and the NFS and dhcp clients.

I decided to go for the brute force approach of reconfiguring the kernel to include the required NIC drivers, NFS and NFSroot support, and that seems to do the job. I can boot using pxe, in exactly the same way as terminal_service works, and then the frontend starts to use the uncompressed root sitting in a directory on the backend.

I have got it all "nearly " working. Problem I have is that although it boots the root filesystem from the nfs server, the root stays read only, so lots of things go wrong. I am exporting the nfsroot rw, but that doesnt seem to help.

So got nearly there, but not quite.

I ran into a problem where I was getting so far through the boot process as root, but then started having access problems. When you create the image, there's an option to enable root access. I believe the default is to NOT allow root access.

So you'll boot up as root, and it will only give you read access. I've been using the terminal_server script included on the KnoppMyth CD, and it presents the option as a check-box during the setup. If you're creating the image using another method I'm not sure where the option would be hiding.

Thaks for the reply, but I am not creating an image at all. I am attempting to get an NFSroot working, where the whole filesystem is sitting on the NFS server, so a directory such as
/myth/terminal_server/nfsroot for instance contains all the filesystem you would usually see on /dev/hda1 in Knoppmyth.

The really cool thing is that I just got it working ! The export command was missing the no_root_squash flag, which stoped me having root priviliges, same i think as you were suggesting.

Once I get over the shock of it actually working I wil post some proper instructions.

Sounds great. I look forward to the writeup. I never got any further than what I wrote up on the wiki. Feel free to replace what I wrote there if you like.

I can see that this could be taken even further by mounting /usr and /bin shared with the backend and having individual /home /etc /var et. al. for each FE.