User often asked, "Why don't work my config with ..." and other users
pointed they into the error log on console.
Errors, Warnings and normal messages are to many, that a fresh starting
user not finds the truely condition for a problem. Or the error was to
late after, so somebody often never was thinking, that it can be a
For example you write
This would simple not boot. You will get this error after the kernel
boot was done. The warning would be scrolled out of your screen. Mostly
users would search for errors only on the file name, not on the indexes.
That's why it was changed from "warning" into "error and stop".
On 26.11.2008 14:46, Paolo Minazzi wrote:
> For me both solution are good. It depends on personal taste ;=)
> In my opinion the best solution is that every admin had her config.
> On Wed, Nov 26, 2008 at 8:37 AM, Shyokou Ouyou wrote:
>> Just read the file, "NEWS.txt", and found a line under the section, "Console
>> and daemons", of "Version 0.7.2", stating, "Stop with error, if double
>> defined device (cobd,cofs,eth,exec)" ... but I think it would be better
>> if the so-called "double defined" can be tolerated as a feature in a config
>> file, dont you?
>> On most of the boxes running coLinux/Linux here in this lab, two or more
>> admins might modify the same config file; but they all keep the original one
>> intact as the default backup, while adding their individual sections as if
>> the parameter(s) "double defined" ... why ? at least, it is easy to read
>> both the default and the modified parameter(s), and even easier to port some
>> similar modifications with a single "diff -urN"; meanwhile, as a one-way
>> modification, in some circumstances, it is easy to automatically update
>> config file using patch algorithm.
>> I wonder if it is acceptable to just warn about "double defined" rather than
>> "Stop with error", and to be compatible with most of the script style config
>> file, latter definition overrides any former one.
>> Shyokou Ouyou