> welcome to the "ignore" list of many developers.  You aren't even
> following directions on how to hurt yourself properly without wasting
> people's time.

I always found that people waste my time when they write explanations
and tons of bla bla that does not have to do with the issue itself,
instead of just writing about what the problem really is.

Because of the permanent repeating of "USE THE GENERIC KERNEL" instead
of answering any questions that have to do with my problem:

Total available disk space on the target system: 32MB

The GENERIC Kernel of OpenBSD 5.0 is >8MB.

I really do a lot to save every bit I can. I delete all programs that
are not constantly needed from disk and compress seldom used programs
and have wrappers that unzip these compressed in case they are needed.
And so on. I don't want to bore you with details, but just take this: I
need it and ...

> I probably have a lesser machine in production.

I'd go for that bet!


And pppppllllllleeeeeeaaaaasssseee don't come up now with "use different
hardware"!!!

There are hundreds of things to think about when it comes to the
hardware you'd be using for a certain purpose. And please don't make me
explain why exactly this hardware is needed for this purpose.

I've got all that running perfectly since OpenBSD 3.5. I've used custom
kernels with success ever since, but with always spending a lot of time
fiddling with which driver to use and which to get rid of. Now I'd like
to find a more convenient way to generally solve this issue.

If you guys say that there is no convenient way of solving this problem
but to really dig into this and completely understand the architecture -
then I still believe that I'll find a working config by fiddling around
and trying this and that until I succeed. I just hoped I'd get a hint
how to ease this process.

T.

Reply via email to