Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
This one is a message you should rarely, if ever, see. Here is its history. Rush needs a list of the filesystems a holder may rest on, together with the words the kernel uses to describe each one. Once, that list lived in a declaration file that the engine read when it was born. If the file was unreadable, or had a group without a word, or a word listed twice, or a missing default, the engine had no clear statement of where data may live. So it refused to be born at all. It would not fall back to a hidden copy of the list written in another language, because two sources of truth always drift apart. Today the list is built into the engine itself, so this refusal no longer fires. But the lesson is still worth knowing. When rush cannot trust the table that defines where your data may rest, it stops at the door, instead of guessing. The first slot names the declaration, the second tells what was wrong. If it ever appears again, fix the declaration, and the engine will start cleanly.
Text from the Rush engine's error catalogue.