Copy2ram unknown operand revisited!

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Copy2ram unknown operand revisited!

Post#1 by nanZor » 21 May 2019, 10:50

I've got some interesting info that might help track this down. Seems that the usual "sh: y: unknown operand" when seen at the boot splash can be changed to read:

sh: sdb: unknown operand

That change from y: to sdb: seems to be caused by putting anything after copy2ram in the append line. I put fsck right after copy2ram just in case I crash, and saw this pop up.

Not a showstopper - seems cosmetic.
That's a UNIX book - cool. -Garth