Tiny Core Base > TCB Q&A Forum

tc-terminal-server and persistence

<< < (5/6) > >>

tinypoodle:
Not very sure what is not clear...
I could not spot a difference between the description of your procedure not working and my procedure proven to be working.

gmc:

--- Quote from: tinypoodle on May 15, 2013, 11:43:06 PM ---Not very sure what is not clear...
I could not spot a difference between the description of your procedure not working and my procedure proven to be working.

--- End quote ---

Got it!  Now I understand what you don't understand!

Are you using TCL 4.7.7?  Maybe the changed tc-terminal-server script has something to do with it?  Just a thought...

Ansyway, I booted from CD with 4.7.7, installed to sda1(DOM), rebooted and ran tc-terminal-server.  Once that was up and running I deleted the three files from /netboot, ran the ln... command verbatim (copied it from your post and pasted it into aterm just to be sure I got it right).  I modified it for core.gz and vmlinuz, verified that the symlinks were actually in the /netboot directory and tried a client PXE boot.

When that did not work I deleted pxelinux.0 symlink and replaced it with the original pxelinux.0.  The PXE client found that file but stalled on core.gzz.

Replace dcore symlink with actual source file.  PXE client stalled at not finding vmlinuz.

Replaced vmlinuz symlink with source.  PXE client booted normally again.

Anything else I can add to make it any clearer?  This would not be so important but I only have 113MB of DOM space available on a clean install.  It disappears very rapidly when I start installing apps, backing up files, etc.

Rich:
Hi gmc

--- Quote ---ln -s /usr/share/syslinux/pxelinux.0 /netboot/
--- End quote ---
Can you double check that path? Syslinux.tcz lists:

--- Code: ---/usr/local/share/syslinux/pxelinux.0
--- End code ---

tinypoodle:
No, I haven't tried latest version and my examples may be inaccurate or outdated, but all that does not change anything about the principle of replacing files by symlinks.

My guess would be what gerald_clark already hinted, that symlinks are not resolved properly.

You might want to consider trying to create symlinks using drag'n'drop with an app like rox, where you get visual interaction and feedback.

Clarification: I only use absolute symlinks, not relative ones.

gmc:

--- Quote from: Rich on May 16, 2013, 12:50:25 AM ---Hi gmc

--- Quote ---ln -s /usr/share/syslinux/pxelinux.0 /netboot/
--- End quote ---
Can you double check that path? Syslinux.tcz lists:

--- Code: ---/usr/local/share/syslinux/pxelinux.0
--- End code ---

--- End quote ---

Yes, double checked and verified.  For what it is worth, I replaced the pxelinux.0 in /netboot with the one from /usr/local/share/syslinux and PXE boots still worked, so I believe I am sourcing the symlink from the correct pxelinux.0

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version