Re: init.d-script in 2.4.33pre?

Peter T. Breuer wrote:

>"Also sprach Bas van Schaik:"
>  
>
>>In general: is there something like a bug tracking system for enbd? I
>>    
>>
>
>I presume that sourceforge has one.  I've never used it. Indeed, debian
>has one! (ditto). The major bugs are things I know about and would be
>embarassed to discuss, such as that remote ioctls weren't working on 64
>bit platforms last time I looked (probably a 32 bit field somewhere
>cramping their style), and there is a slight tendency to produce 
>an oops if the module is removed on a 2.6 platform while requests are
>still in flight, or possibly when breathing too hard. And umm, what
>was that report here from a couple of weeks ago that I was trying to get
>time to look at ....
>
>  
>
>>can't find one on the website, and I think it can be very useful,
>>because more and more people are using enbd. If necessary I can arrange
>>a bugzilla/flyspray/whatever installation on a stable location, so just
>>let me know.
>>    
>>
>
>If you'd like to do that, great! But the problem is using one, not
>there being one. I get nagged enough on the list to make me do things.
>The point, I think, is that minor bugs are so easy to fix that I'd do
>it at once, while major bugs are so difficult to fix that I'd need
>paying. Can you think of a way to engage with that human problem?
>  
>
Hmmm... Good point, I'll have to sleep a night about that ;). However:
my offer stands, so if you find a way to manage your personal human
problem, just let me know :P.

-- Bas