Tiny Core Base > TCB Q&A Forum
tc-terminal-server and persistence
gmc:
--- Quote from: tinypoodle on May 16, 2013, 04:09:27 AM ---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.
--- End quote ---
Agreed, and it is a principle I want to apply here.
--- Quote from: tinypoodle on May 16, 2013, 04:09:27 AM ---My guess would be what gerald_clark already hinted, that symlinks are not resolved properly.
--- End quote ---
Maybe I should do a packet trace and see what is actually being sent as the file name? That might be very revealing...
--- Quote from: tinypoodle on May 16, 2013, 04:09:27 AM ---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.
--- End quote ---
I'll do it.
--- Quote from: tinypoodle on May 16, 2013, 04:09:27 AM ---Clarification: I only use absolute symlinks, not relative ones.
--- End quote ---
Good point, thanks.
genec:
--- Quote from: gmc on May 16, 2013, 05:51:00 PM ---
--- Quote from: tinypoodle on May 16, 2013, 04:09:27 AM ---My guess would be what gerald_clark already hinted, that symlinks are not resolved properly.
--- End quote ---
Maybe I should do a packet trace and see what is actually being sent as the file name? That might be very revealing...
--- End quote ---
1) Different tftpds may respond differently with symlinks. If run chroot-style, it won't resolve the symlinks at all. I recall having to do a bind-mount which I think was for a tftpd configured to do a chroot after start.
2) If the tftpd has /netboot as its root and you want to boot /netboot/pxelinux, specifying "pxelinux.0" for the DHCP/BOOTP field file is perfect.
gmc:
--- Quote from: genec on May 17, 2013, 08:59:14 PM ---1) Different tftpds may respond differently with symlinks. If run chroot-style, it won't resolve the symlinks at all. I recall having to do a bind-mount which I think was for a tftpd configured to do a chroot after start.
2) If the tftpd has /netboot as its root and you want to boot /netboot/pxelinux, specifying "pxelinux.0" for the DHCP/BOOTP field file is perfect.
--- End quote ---
Hi genec,
In answer to #2 above: "If the tftpd has /netboot as its root..."
It does.
"...and you want to boot /netboot/pxelinux..."
I do.
I am including my udhcpd.conf file. Perhaps that is what you are refering to?
udhcpd.conf:
=========================
# The start and end of the IP lease block
start 192.168.0.111
end 192.168.0.122
# The interface that udhcpd will use
interface eth0
boot_file /pxelinux.0
opt dns 192.168.0.1
option subnet 255.255.255.0
opt router 192.168.0.1
option lease 864000 # 10 days of seconds
option tftp 192.168.0.17
siaddr 192.168.0.17
===========================
EoF
Of course pxelinux.0 is only part of the problem, core.gz and vmlinuz can't be found when symlinked, etiher. I don't know if that will make any difference or not in relationship to what you wrote.
Please know that what I say next is said with all kindness and admiration, no sarcasm here.
You are obviously highly intelligent and very knowledgeable about linux (which I admire and am envious of). But this mere mortal is way below your esoteric knowledge base. Could you, would you, translate what you just wrote into something I might be able to comprehend? Maybe with an example or two? I think I can almost make sense of it but a bit more help would maybe, just maybe get me over the top.
Thanks so much for taking the time to give the information you have already, and thanks for any further clarification you may give.
genec:
gmc, thank you.
1) There's no need for the leading "/" generally on your filename.
2) What you're seeing is exactly what I spoke of (and others have alluded to). If "/netboot/vmlinuz" is a symlink with a value of "/path/to/vmlinuz" and the tftpd operates chroot style in /netboot, it'll hunt for the file "/netboot/path/to/vmlinuz". There are 4 basic resolutions:
a) copy the files to /netboot.
b) change the tftpd's root to another directory. This probably won't save any RAM assuming all of the files are in the rootfs in RAM (unless you wanted to drop all of your files in 1 directory on persistent storage).
c) use another tftpd. This would require that you disable dnsmasq's built-in tftp and use another like atftpd/tftpd-hpa.
d) use a hard link (which is 2 filenames pointing to the same file data) rather than a symolic link (which is just special text saying what other path to examine) and works reasonably within 1 file system but can be very dangerous across file systems (extensions are additional file systems)
If you have persistent storage you can use for the files, option (b) is probably your best bet. Otherwise, option (a) is probably the easiest (at least for the moment) seeing as you've already got the beginnings of something working.
gmc:
@genec
I have been taking a short break from this issue while I try to get Xorg set up for larger fonts/desktop, etc. I didn't want you to think I was ignoring your last post. I have been thinking about which of your options would be best for my situation. Once I have my desktop setup working the way I need it then I can focus (pun intended) on this issue again.
In the meantime, thanks for your help.
Navigation
[0] Message Index
[*] Previous page
Go to full version