Tinycore 5.0.1 PXE not loading correctly

[Triorieel]

my pxe default
    KERNEL tinycorepxe/vmlinuz
    APPEND initrd=tinycorepxe/core.gz showapps tftplist=172.16.254.251/tinycorex86/tcz.lst

vmlinuz, core.gz and all the tcz's come from the iso.  tcz.lst is the renamed boot.lst from the iso.

I tried the exact same setup with the older 4.7.7 with no problems

video: http://www.youtube.com/watch?v=499OwRikrMg&feature=youtu.be
Note: Youtube's internal scaling created the aliasing

When starting the recording the video is at the xvesa screen.
I then tell virtualbox to restart.

At the end, X changes resolutions and you can not see that wbar has loaded properly.

I can ping domain names like www.google.com from the terminal.

Problems
-a few errors on startup during tcz loading
-always asks for xvesa and mouse setting
-no background image
-can not load app browser

[gerald_clark]

You can't just rename onboot.lst to tcz.lst.
Please read http://wiki.tinycorelinux.net/wiki:netbooting

[Triorieel]

I have read that article many times over as well as others.
I am not sure what I am missing.

I do not want persistence, so I do not want the extra baggage of nfs.
This method I am using works for previous versions of tinycore (I reverified this earlier by grabbing 4.7.7 which runs without a hitch). 5.0.1 does download and appears to OK all tcz's with a couple can't chdir to home directory.
I think it might be a permissions issue or missing folder at this time (I tried user=root, but this created different problems)

tcz.lst is a list of tcz files I want to load.  onboot.lst is a list of tcz files the iso wants to load.  I want to load the same tcz's as the iso.  I didn't find anything on the page that said I couldn't do this.  I have also done a ls > tcz.lst which has made no difference.

[gerald_clark]

 APPEND initrd=tinycorepxe/core.gz showapps tftplist=172.16.254.251/tinycorex86/tcz.lst
That is just plain wrong.
You have no colon between the server and file.
The file must be relative to the tftpd root directory.
The files listed in the tcz.lst must be relative to the tftpd root directory.

What you currently have cannot possibly work.

[Triorieel]

You are correct.  I was missing the colon

Despite it missing the colon it is was still able to grab the tcz files. (The youtube video above shows this)

Adding the colon does not change anything (but I will keep it in to be proper)

My tcz.lst does properly point to the tcz files (this is verified by the boot process showing the files downloading with progress and resulting in OK)

[curaga]

It's a legit bug, the home rework means the tc user's home does not exist at that point. Thanks for reporting.

Ping Robert.

[gerald_clark]

tftplist and httplist were not intended for general extension loading.
They exist to load extensions necessary to allow the activation of network filesystems such as
NFS AOE and NBD.
These filesystems can then be used as the tce directory or as opt or home.
You cannot have the tc user's home directory available before the filesystems are mounted that host them.

--- Edit ---
The default /home/tc is created before the tftplist is processed, so that is not the problem.
If the home= boot option is specified it is mounted over the default /home/tc.

--- Edit ---
I see that the mkdir was removed in 5.0.1.

[roberts]

Being addressed for 5.0.2

[genec]

Triorieel, I'm glad to see you got a response over here and that it wasn't just you.