yes, but that's not your problem, that's the STR folks' problem.
a simple .config flag is perfectly fine for that, as long as it's
default disabled and properly demarked. We have literally _dozens_ of
"dangerous" test options and _nobody_ complains about them being
dangerous ... They do their primary job of triggering bugs sooner,
faster and harder, resulting in bugs getting fixed sooner, faster and
harder.
no distro would enable this option, it just adds a needless 5-6 seconds
delay to the bootup, and a needless "s2ram blows up sooner than it
should" risk. _I_ want to enable this option, and want to see it trigger
more often than just once out of a hundred randconfig setups.
really, you are making rookie mistakes in this area and you are doing
injustice to the code you wrote and maintain :-) As i said it before,
externally it looks like as if you intentionally avoided your code from
being used, from people who _want_ to use your code. _I_ had to fight
for almost an hour (!) until i figured out the zillions of .config
variants that were finally able to get my test-system to boot-time
suspend and resume all by itself. It's totally non-obvious. As far as
the general Linux community goes, it's almost as if your code did not
even exist, so well hidden and obscured it is.
Ingo
--
